[Octave-bug-tracker] [bug #49383] Command-line options counted as as input arguments when started as an application but not when running scripts

[Mike Miller]

Update of bug #49383 (project octave):

                  Status:                    None => Works For Me           

    _______________________________________________________

Follow-up Comment #2:

Thanks for your bug report, but I'm not sure that you're describing a bug
rather than a feature or a misunderstanding.

I also don't see any inconsistency between Octave 4.2 and previous versions of
Octave wrt nargin and command line arguments. Can you give an example that you
believe shows a difference from previous Octave versions?

Yes, running an Octave executable "script" or "program" from the command line,
as in


$ ./mytest.m

or

$ octave -qf mytest.m


is slightly different from running a script or function in Octave by name, as
in


$ octave
octave:1> mytest

or

$ octave --eval mytest


    _______________________________________________________

Reply to this item at:

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

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