[Octave-bug-tracker] [bug #31287] Certain assignments of empty arrays give errors (Matlab incompatibility)

[Jaroslav Hajek]

Update of bug #31287 (project octave):

             Assigned to:                    None => highegg                

    _______________________________________________________

Follow-up Comment #11:

OK, bravo, you've carried it much farther than I expected. Well done :)

So I guess we all see that these rules are stupidly complex and probably most
of them result from ad hoc implementation decisions. Since I think people
mostly complain when some expression works in Matlab but fails in Octave, I'd
say let's pick a reasonably simple ruleset generalizing these, i.e. let's be
incompatible on the side of allowing more than Matlab.

Options:
A. Allow any empty assignment.
 - Simple, but maybe too simple.
B. Allow any empty null assignment, and for non-null assignments implement
the rules 2.1 and 2.2 observed by Olaf.
C. Like B, but follow 1.1, 1.2 and 1.3 for null assignments, simplifying 1.3
to "logical array with all false elements".

My personal preference is B. Opinions?

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?31287>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/