263
edits
Online Developer Meeting (2022-02-22): Difference between revisions
Online Developer Meeting (2022-02-22) (view source)
Revision as of 02:25, 22 February 2022
, 22 February 2022→Release process of Octave 7.1
m (→Release process of Octave 7.1: minor changes) |
|||
| Line 11: | Line 11: | ||
* Good progress on some of the blocking issues by jwe. Most important remaining ones: | * Good progress on some of the blocking issues by jwe. Most important remaining ones: | ||
** 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. Not started yet. | *** The <code>:</code>-operator will probably be changed to return an array (instead of a range object) before Octave 7. Not started yet. jwe summarized options for the release in comment #18 of the bug report. | ||
** 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 | ||
*** @jwe | *** @jwe check in a fix that will also revert to copying data in the .mex interface (less efficient, but also the way it has always been done until now) unless Octave is compiled with C++17 pmr. | ||
** bug {{bug|61821}}: segfault using tree_parameter_list in oct file | ** bug {{bug|61821}}: segfault using tree_parameter_list in oct file | ||
*** Lower priority, only 32-bit (only on Windows?). Probably not a blocker. | *** Lower priority, only 32-bit (only on Windows?). Probably not a blocker. | ||