240
edits
Online Developer Meeting (2022-01-25): Difference between revisions
Jump to navigation
Jump to search
Online Developer Meeting (2022-01-25) (edit)
Revision as of 09:39, 26 January 2022
, 26 January 2022→Release process of Octave 7.1: Update notes
(→GSOC 2022 opening soon: Notes Kai.) |
(→Release process of Octave 7.1: Update notes) |
||
| Line 10: | Line 10: | ||
* Blocking issues: 9 bugs targeting 7.0.90 (see [https://octave.space/savannah/# Savannah overview on octave.space]) | * Blocking issues: 9 bugs targeting 7.0.90 (see [https://octave.space/savannah/# Savannah overview on octave.space]) | ||
* Most important ones (in no particular order): | * Most important ones (in no particular order): | ||
** bug {{bug|61788}}: arrays of type int16 contain wrong numbers | ** bug {{bug|61788}}: arrays of type int16 contain wrong numbers | ||
*** | *** The <code>:</code>-operator will probably be changed to return an array (instead of a range object) before Octave 7. | ||
** bug {{bug|61813}}: memory management bug when calling MEX that returns an output | ** bug {{bug|61813}}: memory management bug when calling MEX that returns an output | ||
*** | *** Probably caused by changes for more efficient data interface for .mex files. @jwe will check this. | ||
** | ** Possible issues if Octave is compiled with C++17 (<code>--enable-pmr-polymorphic-alocator</code>), while .oct files are not. | ||
** bug {{bug|61821}}: segfault using tree_parameter_list in oct file | *** Maybe change the API string if Octave is configured with polymorphic allocators? | ||
*** | *** Leave that option in. But disable it by default. (That is already the current state.) | ||
** bug {{bug|61898}}: subsref: Error when field syntax is used on non-scalar @class object | ** <code>malloc</code>-<code>delete[]</code> combination in the .mex interface | ||
*** | *** No decision made. Maybe leave as is? | ||
* A few package releases with fixes for Octave 7 were pushed to | ** bug {{bug|61821}}: segfault using tree_parameter_list in oct file | ||
** Should those changes be | *** Check if we are doing something wrong for 32bit. Probably not a blocker. | ||
** bug {{bug|61898}}: subsref: Error when field syntax is used on non-scalar @class object | |||
*** Try finding a minimal reproducer (without interval package). Similar bug {{bug|61843}} reported. | |||
* A few package releases with fixes for Octave 7 were pushed to the default branch of MXE Octave, e.g. https://hg.octave.org/mxe-octave/rev/d601436d29f2 (ga, control, communications) | |||
** Should those changes be grafted to the "release" branch? -YES. | |||
* Revisit load path caching: https://octave.discourse.group/t/rfc-remove-faulty-load-path-caching/2136 | * Revisit load path caching: https://octave.discourse.group/t/rfc-remove-faulty-load-path-caching/2136 | ||
** Improving the caching strategy is the way to go. | ** Improving the caching strategy is the way to go (see e.g. bug {{bug|54636}}). | ||
** Long-term: A complete overhaul of the load path caching implementation is probably necessary. | |||
=== C++17 features in Octave API? === | === C++17 features in Octave API? === | ||