|
From: | Philip Nienhuis |
Subject: | [Octave-bug-tracker] [bug #47021] Calling nargin for scripts returns wrong error message |
Date: | Sun, 31 Jan 2016 19:08:05 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux i686 on x86_64; rv:41.0) Gecko/20100101 Firefox/41.0 SeaMonkey/2.38 |
Update of bug #47021 (project octave): Item Group: Inaccurate Result => Incorrect Result Status: Fixed => Confirmed Open/Closed: Closed => Open Release: 4.0.0 => dev _______________________________________________________ Follow-up Comment #4: Reopening. On reading more closely (sorry Daniel for noting only now; good that you hinted again in comment #2) I can confirm this. In Octave-4.1.0+, with a script g.m s follows: ## This is a scipt file printf ("This is g.m\n" ); I get: >> g This is g.m >> nargin (g) error: invalid call to script /home/philip/tmp/g.m >> nargin (@g) error: nargin: nargin information not available for built-in functions >> Admittedly script files (not function files) aren't supposed to have input or output arguments; but Octave's reaction (interpreting "g" as a built-in function) is beside the point. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?47021> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |