[Octave-bug-tracker] [bug #65532] '[=]' is deprecated

[Markus Mützel]

Follow-up Comment #3, bug #65532 (group octave):

Sorry if the pointer to bug #65318 wasn't verbose enough.

This has already been "fixed" on the default branch while handling that other
report:
https://hg.savannah.gnu.org/hgweb/octave/rev/489026b7257b

To be honest, I don't understand what the issue in the lines you cited should
be. At a current head, they contain completely unrelated things (e.g., a
comment):
https://hg.savannah.gnu.org/hgweb/octave/file/c61aadb5b676/libinterp/parse-tree/pt-eval.cc#l1166

      // exception occurred, not just throwing an


As a maybe related note in case you are looking at the sources of an older
release: There is only one stable release that is maintained by the Octave
community at a time. At the moment that is Octave 9.1.0.
Until very recently, Octave was using C++11 as the C++ standard (with some
features of newer standards in mind). Only very recently, this was changed to
C++17 (for a future version of Octave).
This is not really a "bug", but a side-effect of a decision from the standards
committee to make a backwards-incompatible change. Additionally, I'm not aware
of any compiler that sets the default to C++20 in a current version.
Nevertheless, changes were made to make the code compatible to the newer
standard.
Because the "work-around" is easy (compile with a compatible standard), those
changes went on the default branch (which will likely be released as Octave 11
some time early 2025).



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?65532>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/