[Octave-bug-tracker] [bug #54698] Precedence of call/indexing operator over transpose operator

[anonymous]

Follow-up Comment #26, bug #54698 (project octave):

@John W. Eaton 
Please read my proposed change to table of precedence in commnet13
<https://savannah.gnu.org/bugs/index.php?54698#comment13>. After extended
discussions I have found it to be the best solution and it is completely
compatible with the current behavior of Octave.

= is OK
I think ()  means the parenthesis operator instead of call operator . As it
can be used to group sub expressions: a+b*c  ===> a+(b*c)

I agree that compound operators like .^- are the only way to work around
otherwise troublesome precedence rules. But I don't know why they have changed
its "L to R" order of evaluation to "R to L" ??

Those operators cannot be overloaded because there is no functional form of
them and they don't have any name!!

I now have accepted that rearranging is a wrong idea.
I believe that indexing on temporary is a nice thing.

I have proposed 3 compound operators to be documented as I think they are the
only way to work around otherwise troublesome precedence rules. No change to
the parser is needed.

And that in the documentation the postfix ++/-- should have the same level of
precedence as of the call operator .


    _______________________________________________________

Reply to this item at:

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

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