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

[Jaroslav Hajek]

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

The situation you describe is really special and I can imagine a better
solution on the library's side, such as returning an anonymous or private
function handle containing an error() call.

Other than this weirdness, are there any good reasons why defer the error to
first call? If you misspell a function name, I think it makes a much better
sense to gripe at the point of handle creation, instead of the point of usage,
which can be nowhere near the bug. Besides, with Octave's current
implementation, griping at creation is more natural and more efficient.

I think Octave's behavior is better and I'm against such a change unless you
can bring up better arguments.

    _______________________________________________________

Reply to this item at:

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

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