[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #31287] Certain assignments of empty arrays gi
[Octave-bug-tracker] [bug #31287] Certain assignments of empty arrays give errors (Matlab incompatibility)
Wed, 12 Jan 2011 16:57:45 +0000
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:184.108.40.206) Gecko/20101206 Ubuntu/10.04 (lucid) Firefox/3.6.13
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.
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:
Message sent via/by Savannah