Editing Online Developer Meeting (2022-01-25)
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
* Date: Tuesday, January 25, 2022 @ 18:00 UTC | * Date: Tuesday, January 25, 2022 @ 18:00 UTC | ||
* Location: https://meet.jit.si/octave-dev | * Location: https://meet.jit.si/octave-dev-2022-05-25 | ||
== Todays topics == | == Todays topics == | ||
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 | ** [https://savannah.gnu.org/bugs/index.php?61788 bug #61788: arrays of type int16 contain wrong numbers] | ||
** | ** [https://savannah.gnu.org/bugs/index.php?61813 bug #61813: memory management bug when calling MEX that returns an output] | ||
** [https://savannah.gnu.org/bugs/index.php?61821 bug #61821: segfault using tree_parameter_list in oct file] | |||
** | ** [https://savannah.gnu.org/bugs/index.php?61898 bug #61898: subsref: Error when field syntax is used on non-scalar @class object] | ||
** maybe also: <code>malloc</code>-<code>delete[]</code> combination in the .mex interface | |||
** | |||
** | |||
* 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 | ||
=== C++17 features in Octave API? === | === C++17 features in Octave API? === | ||
* Timeframe? | * Timeframe? | ||
* Should we announce that possible requirement for some time in the future with the release of Octave 7? | * Should we announce that possible requirement for some time in the future with the release of Octave 7? | ||
* See also: [https://octave.discourse.group/t/should-octave-switch-to-c-17-if-so-when/2114 Should Octave switch to C++17? If so, when?] on Discourse. | * See also: [https://octave.discourse.group/t/should-octave-switch-to-c-17-if-so-when/2114 Should Octave switch to C++17? If so, when?] on Discourse. | ||
== Previous topics == | == Previous topics == |