Editing Online Developer Meeting (2021-07-27)

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

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 9: Line 9:
* 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).
*** Done, already answered: https://lists.gnu.org/archive/html/octave-maintainers/2021-07/msg00001.html


=== Octave 6.4 / 7 / 8 ===
=== User expectations for "Evaluate selection" ===
* Discussion how to continue with the development.
** jwe wants to introduce breaking changes (see below).
* Octave should stick with the ~yearly major release cycle
** Probably no Octave 6.4 (only if severe bugs occur).
** Octave 7 (default branch)
*** Should no longer receive "very" breaking changes (e.g. String-class for Octave 8)
*** Has about 305 bugs fixed (not 100% reliable figure) and should not wait another year until many bigger outstanding changes happen (will be deferred to Octave 8)
*** Tentative plan:
**** November 2021 merge default to stable.
**** End of 2021 release of Octave 7
** Octave 8 (new default branch)
*** No clear decision how to handle very breaking changes until November 2021 merge default to stable.  Depends on future needs.


=== Octave 7 / 8 ===
* [https://www.mathworks.com/help/matlab/ref/arguments.html Function argument parsing] (introduced in Matlab R2019b, rather new)
** 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.
* [https://octave.discourse.group/t/new-command-window-widget/501? New GUI command widget]
** Possible to introduce it as user opt-in in Octave 7
** Pending issues:
*** Command-widget does not look like the previous one (textbox for command input)
*** jwe needs better looking widget (avoid developing a new one)
*** No possibility to run external applications (like emacs, pager), which is already partially broken now.  Need to implement own paging strategy (scroll bars, etc.)
* Deprecation of Octave operators
** Improve Matlab compatibility
** Some extensions make it painful to implement Matlab compatible command-style function calls?  See also the [https://octave.discourse.group/t/parsing-command-style-function-call-syntax/1414/7 discussion] about this topic.
*** Remove rarely used extensions like "**" power.
*** Discussion about removal of "+=", "++", etc.  No final decision made.
*** Often used extensions must probably stay (like "!" or "!=" used in place of "~" or "~=").
=== C++ shared pointer / liboctave ===
* jwe had a look at Octave own reference counting
* Wish to replace it with C++ shared pointers
* Expert knowledge wanted!  jwe opened a [https://octave.discourse.group/t/using-std-shared-ptr-t-to-implement-copy-on-write-objects-in-octave/1436 discussion thread]
* jwe identified "copy expensive" inefficiency about mxArray to octave_value conversion? Root of the trouble lies in historical handling of complex data?  See this [https://octave.discourse.group/t/improving-performance-of-data-transfer-to-and-from-mex-functions/1437 discussion].


== Previous topics ==
== Previous topics ==
Line 85: Line 50:
* <strike>jwe will probably post something on discourse.</strike>
* <strike>jwe will probably post something on discourse.</strike>
* See: [https://octave.discourse.group/t/irc-channel-for-octave/1348 IRC channel for Octave] (on Discourse).
* See: [https://octave.discourse.group/t/irc-channel-for-octave/1348 IRC channel for Octave] (on Discourse).
== Ideas for next meeting ==
*


== See also ==
== See also ==
Please note that all contributions to Octave may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Octave:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)
Retrieved from "https://wiki.octave.org/Online_Developer_Meeting_(2021-07-27)"