[Octave-bug-tracker] [bug #47807] run behaves differently from Matlab on function m-files

[Julien Bect]

Follow-up Comment #3, bug #47807 (project octave):

> it seems simple enough to add if it's an important feature to someone.

I already lost some valuable time understanding this, so at least it's
important to me ;-)


> Does Matlab also change directory to the location of the function file

Yes, Matlab changes directory in all cases.


> Does it show an error for functions that do require arguments?

Yes, exactly the same error that you get if you call the function directly: if
the function actually uses the argument, you get an error; otherwise, no.


> Do errors occur in the same context as if the function were just called
without run?

Not sure what you mean.  I think the answer is no: you can see that run() has
been called in th dbstack (run only, nothing else).


> Can errors be caught with try or shown with lasterr?

Yes (both).




    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message posté via/par Savannah
  http://savannah.gnu.org/