[Top][All Lists]

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

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

From: Jaroslav Hajek
Subject: [Octave-bug-tracker] [bug #29447] Cannot create @handles to non-existing functions
Date: Wed, 07 Apr 2010 05:47:16 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8

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

By the way, is this a documented behavior of Matlab? I couldn't find it
anywhere. Matlab docs say that a handle stores an absolute path to a function
file, from which I imply that cd to a different directory should make no
difference in subsequent calls. So, what is stored if no function can be
Btw, which version did you use in your test?

Weird tricks done by libraries are probably < 1% of the occurences of
non-existing handles. The remaining 99% are names that were simply misspelled,
or missing functions or packages. In these cases, it makes much more sense to
throw an error at the point where the handle is created, because that's where
the bug actually is. Sometimes this is the same line where the first call
occurs, but it may not be. 

Maybe the reason why niftimatlib does this is so that you could write your
own error handler? In that case, I'd say just do it. Maybe you can convince
them to do it directly in the library? After all, it seems that you will get
something like "undefined function or variable 'crash'" from Matlab, which is
not really an informative error message here.

I feel a bit tired of defending the common sense against Matlab quirks. Go
ahead and "fix" this if I didn't convince you. It would be nice if it could be
turned off by a global pseudo-variable, however.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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