Editing Online Developer Meeting (2021-08-24)
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 6: | Line 6: | ||
* Meet and greet 5 minutes before meeting (audio testing). | * Meet and greet 5 minutes before meeting (audio testing). | ||
=== | === First topic to discuss === | ||
== Previous topics == | == Previous topics == | ||
Line 55: | Line 14: | ||
* No "official" announcement happened. Maybe reuse abandoned mailing-lists to announce important events, such as releases. | * No "official" announcement happened. Maybe reuse abandoned mailing-lists to announce important events, such as releases. | ||
* How do distribution maintainers get to know about Octave releases? | * How do distribution maintainers get to know about Octave releases? | ||
** Contact Debian maintainers of the Octave package to maybe improve our communication. | ** Contact Debian maintainers of the Octave package to maybe improve our communication (Kai). | ||
=== Octave 6.4 / 7 / 8 === | === Octave 6.4 / 7 / 8 === | ||
Line 76: | Line 34: | ||
** jwe will continue to work on this feature on Octave 7 (default branch) | ** jwe will continue to work on this feature on Octave 7 (default branch) | ||
** If feature cannot be completed by the end of the year, it will be disabled on parser-level (error), and introduced in Octave 8 one year later. | ** If feature cannot be completed by the end of the year, it will be disabled on parser-level (error), and introduced in Octave 8 one year later. | ||
* | * New GUI command widget | ||
** Possible to introduce it as user opt-in in Octave 7 | ** Possible to introduce it as user opt-in in Octave 7 | ||
** Pending issues: | ** Pending issues: | ||
Line 84: | Line 42: | ||
* Deprecation of Octave operators | * Deprecation of Octave operators | ||
** Improve Matlab compatibility | ** Improve Matlab compatibility | ||
** Some extensions make it painful to implement Matlab compatible command-style function calls? | ** Some extensions make it painful to implement Matlab compatible command-style function calls? (some clarification needed) | ||
*** Remove rarely used extensions like "**" power. | *** Remove rarely used extensions like "**" power. | ||
*** Discussion about removal of "+=", "++", etc. No final decision made. | *** Discussion about removal of "+=", "++", etc. No final decision made. | ||
*** Often used extensions | *** Often used extensions like "!" == "~" must probably stay. | ||
=== C++ shared pointer / liboctave === | === C++ shared pointer / liboctave === | ||
* jwe had a look at Octave own reference counting | * jwe had a look at Octave own reference counting | ||
* Wish to replace it with C++ shared pointers | * Wish to replace it with C++ shared pointers | ||
* Expert knowledge wanted! | * Expert knowledge wanted! | ||
* jwe identified "copy expensive" inefficiency about mxArray to octave_value conversion? Root of the trouble lies in historical handling of complex data? | ** jwe will reach out on Discourse about the exact problems. | ||
* jwe identified "copy expensive" inefficiency about mxArray to octave_value conversion? (some clarification needed) | |||
** Root of the trouble lies in historical handling of complex data?? (some clarification needed) | |||
== See also == | == See also == |