254
edits
Online Developer Meeting (2021-12-28): Difference between revisions
Online Developer Meeting (2021-12-28) (view source)
Revision as of 20:22, 28 December 2021
, 28 December 2021Update notes from meeting.
(Update notes from meeting.) |
|||
| Line 8: | Line 8: | ||
=== Release process of Octave 7.1 === | === Release process of Octave 7.1 === | ||
* | * No blocking issues at the moment. | ||
* Translations | ** 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. | |||
* 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 <code>@seealso</code> links to point to old class functions - like <code>@ftp/open</code>. (Doesn't work currently in doc cache.) | |||
* Lookup classdef methods for help and debugger. | |||
* Check reason for "disappearing" classdef constructor for MException class: [https://savannah.gnu.org/bugs/?40828 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 === | === Update strategy for MXE Octave === | ||
| Line 16: | Line 38: | ||
* <code>default</code> branch was merged to <code>release</code> a couple of weeks ago. That was meant to get the CI working after the merge from <code>default</code> to <code>stable</code> in the main Octave repository. It was '''not''' meant to freeze the branch... | * <code>default</code> branch was merged to <code>release</code> a couple of weeks ago. That was meant to get the CI working after the merge from <code>default</code> to <code>stable</code> 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? | * 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 === | === Status of plotting in Octave === | ||
* https://octave.discourse.group/t/plotting-backend-for-web-ui/2008 | * 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. | |||
== Previous topics == | == Previous topics == | ||