Online Developer Meeting (2022-01-25): Difference between revisions
Jump to navigation
Jump to search
(Create page.) |
(No difference)
|
Revision as of 08:46, 29 December 2021
- Date: Tuesday, January 25, 2022 @ 18:00 UTC
- Location: https://meet.jit.si/octave-dev-2022-05-25
Todays topics
- Meet and greet 5 minutes before meeting (audio testing).
Previous topics
- The following items were not discussed. Just some links to progress on those items are displayed.
Release process of Octave 7.1
- No blocking issues at the moment.
- Visibility flags are disabled (on the stable branch).
- Polymorphic allocators are disabled by default, but can be enabled with a configure switch.
- Translations are still ongoing.
- Update year in copyright notes.
- Do a first release candidate during the next few days (independent on current status of translations).
Projects for Octave 8
- Array<T> template class:
- Allow implicit instantiations
- Less explicit instantiations (where possible)
- Background: Current design of requiring explicit instantiations was probably "just" for optimization of compile time.
- Make sorting a part of the Array<T> template (instead of a separate template).
- Background: At the time, this was first implemented, there was (probably?) no good sorting method in the STL.
- Maybe move to C++ sorting methods now if possible.
- provide STL compatible iterators (might be a requirement for STL sorting)
- generally try to take better advantage of templating and specializations.
- Make it explicit in the docstring if functions have a return argument.
- Allow
@seealso
links to point to old class functions - like@ftp/open
. (Doesn't work currently in doc cache.) - Lookup classdef methods for help and debugger.
- Check reason for "disappearing" classdef constructor for MException class: bug #40828
- Is it possible to simplify the implementation of classdef in Octave core?
- General note on changes: Don't over-complicate code for micro-optimizations. Use STL where possible and where it makes sense.
Update strategy for MXE Octave
default
branch was merged torelease
a couple of weeks ago. That was meant to get the CI working after the merge fromdefault
tostable
in the main Octave repository. It was not meant to freeze the branch...- When should the "actual" merge happen? For the (first?) release candidate? For the final release?
- Merge some time during the next few days. Before the first release candidate.
- After that, fix bugs as necessary.
Status of plotting in Octave
- https://octave.discourse.group/t/plotting-backend-for-web-ui/2008
- The "gnuplot" graphics interface will eventually be removed.
- It's probably difficult (or impossible) to make it a package.
- The "qt" graphics interface is the default now.
See also
- Next meeting: Online Developer Meeting (2022-02-22)
- Last meeting: Online Developer Meeting (2021-12-28)