[Octave-bug-tracker] [bug #29447] Cannot create @handles to non-existing functions

[Jaroslav Hajek]

Follow-up Comment #19, bug #29447 (project octave):

"...doesn't actually say it is an error to create an invalid handle. It could
be saying that the handle won't work. "

Technically, this is true, but note that the manual uses the wording that
some condition *must* hold at a lot of other places, and usually it means that
violating the condition leads to an error. Admittedly, sometimes it means just
undefined or incorrect behavior, mainly in the cases where the condition can't
be reasonably checked.

"However, I don't think that error() is fundamentally superior to warning()
for notifying the user of the possible typo."

It depends on what you consider "fundamentally", but I think this is not
true. Unlike a warning, error normally produces a traceback to point you to
the place where it occured. Warnings can only do this if you turn them into
errors.
I should add that apparently many Octave users utterly dislike warnings, so
if they ever used niftimatlib, they would probably complain even about the
warning.

In any case, as you said, the manual clearly implies that a program creating
handle to a function that is not in scope is not valid.

    _______________________________________________________

Reply to this item at:

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

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