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

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

[Octave-bug-tracker] [bug #56167] non-existent cell indexing 'C{}' shoul


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #56167] non-existent cell indexing 'C{}' should produce an error
Date: Tue, 23 Apr 2019 06:28:24 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0

Follow-up Comment #13, bug #56167 (project octave):

I'm not sure why x() and X{} are allowed for built-in array objects.  Stranger
still is that x{} works like x{:} for cell array objects.

It does make sense to call subsref for those expressions, but for numeric
objects I think they should be errors.

I noticed there is a test in Cell.cc to ensure that "a() == a" for cell array
objects and that containers.Map relies on that behavior.  What does Matlab do
for


x = {1, 2; 3, 4}
x()


?


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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