[Top][All Lists]

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

[Octave-bug-tracker] [bug #49383] Command-line options counted as as inp

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #49383] Command-line options counted as as input arguments when started as an application but not when running scripts
Date: Tue, 18 Oct 2016 22:43:36 +0000 (UTC)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0

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


$ octave -qf mytest.m

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

$ octave
octave:1> mytest


$ octave --eval mytest


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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