Oh ye the assumption in the code is that nargin is always zero for scripts.

Fix nargin for scripts in bytecode interpreter (bug #65140)

So that nargin calls in scripts properly matches argv or amount of function arguments, instead of always zero.

* stack-frame.cc: Set nargin
* test/compile/bytecode.tst: Do new test
* test/compile/bytecode_script_nargin.m: New test file
* test/compile/module.mk: Add new file

(file #55553)

Using Octave built from the bytecode-interpreter branch, I see the following in an interactive session started with some command line arguments:

$ /path/to/octave --no-init-file --no-line-editing --no-window-system
GNU Octave, version 10.0.0
Copyright (C) 1993-2024 The Octave Project Developers.
This is free software; see the source code for copying conditions.
There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE.  For details, type 'warranty'.

Octave was configured for "x86_64-pc-linux-gnu".

Home page:            https://octave.org
Support resources:    https://octave.org/support
Improve Octave:       https://octave.org/get-involved

For changes from previous versions, type 'news'.

octave:1> argv
ans =
{
  [1,1] = --no-init-file
  [2,1] = --no-line-editing
  [3,1] = --no-window-system
}

octave:2> nargin
ans = 3

That is expected behavior.  However, if I create a script file containing the lines

argv
nargin

I see the following output when passing the name of the script on the Octave command line with extra arguments after the name of the file:

$ /path/to/octave foo.m one two three
ans =
{
  [1,1] = one
  [2,1] = two
  [3,1] = three
}

ans = 0

The value of argv is correct but nargin should be 3 here, not 0.

This affects the way "make check" works if Octave is built in a directory outside the source tree.  In that case, all the tests in files from the source tree are skipped.