1,847
edits
Online Developer Meeting (2022-02-22): Difference between revisions
Jump to navigation
Jump to search
Online Developer Meeting (2022-02-22) (edit)
Revision as of 04:47, 24 February 2022
, 24 February 2022→Todays topics: Add notes and memory of Kai
(Add some topics for upcoming meeting) |
(→Todays topics: Add notes and memory of Kai) |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 8: | Line 8: | ||
=== Release process of Octave 7.1 === | === Release process of Octave 7.1 === | ||
* Blocking issues: | * Blocking issues: 8 open bugs targeting 7.0.90, 3 marked as "ready for test" (see [https://octave.space/savannah/# Savannah overview on octave.space]) | ||
* 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. | *** 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 | *** Image package had trouble with this change (bug {{bug|61815}}). These changes should be reviewed with the next Octave 7 release candidate. | ||
*** @jwe | *** jwe summarized options for the release in comment #18 of the bug report. | ||
** bug {{bug|61821}}: segfault using tree_parameter_list in oct file | *** jwe will revert most changes on "stable" (Octave 7) and continue developing on "default". | ||
*** Lower priority, only 32-bit (only on Windows?). | ** bug {{bug|61813}}: memory management bug when calling MEX that returns an output | ||
*** @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. | |||
*** This also avoids the <code>malloc</code>-<code>operator delete[]</code> mismatch. | |||
*** Confirmed fixed now. | |||
** bug {{bug|61821}}: segfault using tree_parameter_list in oct file | |||
*** Lower priority, only 32-bit (only on Windows?). Maybe a compiler bug? | |||
*** Not a blocker. | |||
** bug {{bug|61898}}: subsref: Error when field syntax is used on non-scalar @class object | ** bug {{bug|61898}}: subsref: Error when field syntax is used on non-scalar @class object | ||
*** Not a bug in Octave core. Recent changes to output argument validation uncovered an issue in interval package. | *** Not a bug in Octave core. Recent changes to output argument validation uncovered an issue in interval package. | ||
** Similar bug {{bug|61843}}: Regression with subscripted assignments with arrays of objects | ** Similar bug {{bug|61843}}: Regression with subscripted assignments with arrays of objects | ||
*** Older regression. | *** Older regression. | ||
** Use suffix for API string when it requires C++17 pmr? | |||
*** Should indicate if Octave was compiled with C++17 support or not. | |||
*** Need to recompile packages. | |||
*** Agreed to avoid suffix. Leave things as is. | |||
** bug {{bug|61687}}: Ignore not updated translations. Open new bug report for further translations. | |||
** '''There will be soon a second release candidate.''' | |||
=== Minimum Qt5 version for Octave 8? === | === Minimum Qt5 version for Octave 8? === | ||
* No real conclusion. Wait for progress with Linux distributions. | |||
* See [https://octave.discourse.group/t/qt5-15-already-unsupported-upstream-except-commercial-license/737/15 Qt5.15 already unsupported upstream (except commercial license)?] | * See [https://octave.discourse.group/t/qt5-15-already-unsupported-upstream-except-commercial-license/737/15 Qt5.15 already unsupported upstream (except commercial license)?] | ||
=== libinterp === | |||
* suggestion to prefer <code>std::copy_n</code> instead of for-loop to duplicate data | |||
** try to avoid making too many copies anyways! | |||
* rik updated about the progress on bug {{bug|61753}} (https://octave.discourse.group/t/project-to-review-and-replace-c-assert-with-error-calls/2043) | |||
** jwe suggest to use [https://en.cppreference.com/w/cpp/language/exceptions proper C++ exceptions] in some future release of Octave, instead of error function pointers. | |||
=== dynamic loader (oct-files) === | |||
* jwe worked on refactoring dynamic code loading with <code>std::shared_ptr</code>, also for reference counting. | |||
* Not clear if there is a portable "standard" way of loading code dynamically (oct-file). Ideas are welcome. | |||
=== (Not discussed) Where to announce package updates now? === | |||
* See [https://octave.discourse.group/t/2246 Do we still announce new OF package releases and if yes, where?] | |||
== Previous topics == | == Previous topics == | ||