octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #30941] truncated subsrefs array in 3.3.52+


From: Jaroslav Hajek
Subject: [Octave-bug-tracker] [bug #30941] truncated subsrefs array in 3.3.52+
Date: Thu, 02 Sep 2010 05:59:04 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/533.2 (KHTML, like Gecko) Chrome/5.0.342.9 Safari/533.2

Update of bug #30941 (project octave):

              Item Group:                   Crash => Incorrect Result       
                  Status:                    None => Wont Fix               
             Assigned to:                    None => highegg                
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #1:

This change is intentional. Matlab doesn't allow two consecutive ()
subscript, while Octave does allow them in expressions (not assignment).
Hence, Matlab class code may not be prepared for such chains. That's why
Octave splits the index chain at that point, to stay compatible yet still
allow indexed expressions.

If you wish to rediscuss this change, please open a discussion at the
maintainers' list.

In any case, if Y = X(1:3, 1)(:).cell is supposed to work differently than Z
= X(1:3, 1); Y = Z(:).cell,
I strongly recommend you revise the design, because that's very confusing
IMHO. If .cell just indicates the type of the desired result, why not make it
X.cell(1:3, 1)(:)?



    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]