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

[Rik]

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

The third patch works fine.

Regarding the coding question, none of the code is performance sensivitive
since it will only be hit if an error has occurred and we are returning to the
interactive prompt.  This says that we should just do it the way we like. 
Your current patch with a temporary variable has the advantage of already
being coded.  On the other hand, if it is easy not to create a temporary
variable, call a bunch of constructors, get memory from the stack for the new
object, etc. then we should do that.

Is the only change really to add "const" to a function declaration?

    _______________________________________________________

Reply to this item at:

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

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