[Octave-bug-tracker] [bug #47021] Calling nargin for scripts returns wrong error message

[Philip Nienhuis]

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/