[Octave-bug-tracker] [bug #46536] Bad indexing could produce more informative error messages

[Lachlan Andrew]

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

Thanks for checking that, jwe.  I'll edit the comment.

The question now is whether more informative error messages are worth the
extra cost of splitting after every  ().  I assume that the evaluation in the
final  subsref()  gets cheaper by about the expense of the code executed if
force_split is true. Is that the case?  I did some experiments with the
following script, and the differences were lost in the noise


for i = 30:-1:1
  for j = 30:-1:1
    for k = 30:-1:1
      for l = 30:-1:1
        a.foo(i).bar(j).cat(k).dog(l) = 1;
      end
    end
  end
end


If so, it seems to me that splitting after every () would be worthwhile.  If
the line is unchanged, it will just mean there are more cases that get 
c...(-1).  What do you think?

    _______________________________________________________

Reply to this item at:

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

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