Mixing
octave 3 vs 4 script compatibility; where's REAL documentation of Executable-Octave-Programs
up vote
1
down vote
favorite
Part-1: In octave 3.4.3 (on centos 6.6) following script file "joe.m":
#!/bin/bash
# for-bash:
#{
exec octave -q --no-init-file "$0" ${1+"$@"}
#}
# for-octave:
function jim ()
printf ("program_name: '%s'n", program_name ());
endfunction
printf ("calling jimn")
jim
produces output:
calling jim
program_name: 'joe.m'
But in octave 4.2.1 it gives a warning, and appears to auto-call(!?) jim, and does NOT run top-level immediate code(!?), no output line "calling jim":
warning: function name 'jim' does not agree with function filename '/tmp/joe.m'
program_name: 'joe.m'
Part-2: If I rename same file to "jim.m", then in octave 3.4.4 the output is:
calling jim
program_name: 'jim.m'
in octave 4.2.1 now warning is avoided, but still missing "calling jim" line.
Part-3: With zero functions defined, the top-level code will execute in both versions.
Where are these behaviors (and this change of behavior from version 3 to 4) documented or controlled? Nothing of the sort is mentioned in:
https://octave.org/doc/v4.2.1/Command-Line-Options.html
https://octave.org/doc/v4.2.1/Executable-Octave-Programs.html
How can one write an octave file compatible with both version 3.x and 4.x, or how to invoke 4.x with an extra option to behave compatibly with 3.x? How to execute top-level code in 4.x even when functions are defined?
How can one deterministically know (without trial and error) what function will be auto-called (and with what arguments) in 4.x without documentation of same? This example not enough to nail it down, since there's one and only one function: if there are multiple functions (joe and jim), does the order matter, relative to whether either or none matches the file name?
Note: the shebang (self-contained script) is just a convenience, not relevant to the question, behaviors are same with or without it.
octave
asked 6 hours ago
bk-se
17515
add a comment |
up vote
1
down vote
favorite
Part-1: In octave 3.4.3 (on centos 6.6) following script file "joe.m":
#!/bin/bash
# for-bash:
#{
exec octave -q --no-init-file "$0" ${1+"$@"}
#}
# for-octave:
function jim ()
printf ("program_name: '%s'n", program_name ());
endfunction
printf ("calling jimn")
jim
produces output:
calling jim
program_name: 'joe.m'
But in octave 4.2.1 it gives a warning, and appears to auto-call(!?) jim, and does NOT run top-level immediate code(!?), no output line "calling jim":
warning: function name 'jim' does not agree with function filename '/tmp/joe.m'
program_name: 'joe.m'
Part-2: If I rename same file to "jim.m", then in octave 3.4.4 the output is:
calling jim
program_name: 'jim.m'
in octave 4.2.1 now warning is avoided, but still missing "calling jim" line.
Part-3: With zero functions defined, the top-level code will execute in both versions.
Where are these behaviors (and this change of behavior from version 3 to 4) documented or controlled? Nothing of the sort is mentioned in:
https://octave.org/doc/v4.2.1/Command-Line-Options.html
https://octave.org/doc/v4.2.1/Executable-Octave-Programs.html
How can one write an octave file compatible with both version 3.x and 4.x, or how to invoke 4.x with an extra option to behave compatibly with 3.x? How to execute top-level code in 4.x even when functions are defined?
How can one deterministically know (without trial and error) what function will be auto-called (and with what arguments) in 4.x without documentation of same? This example not enough to nail it down, since there's one and only one function: if there are multiple functions (joe and jim), does the order matter, relative to whether either or none matches the file name?
Note: the shebang (self-contained script) is just a convenience, not relevant to the question, behaviors are same with or without it.
octave
asked 6 hours ago
bk-se
17515
If the shebang line is not relevant to the question, please remove it. It took me a while to parse that. Let people focus on what is important. See Minimal, Complete, and Verifiable example (especially the minimal part!).
– Cris Luengo
1 hour ago
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Part-1: In octave 3.4.3 (on centos 6.6) following script file "joe.m":
#!/bin/bash
# for-bash:
#{
exec octave -q --no-init-file "$0" ${1+"$@"}
#}
# for-octave:
function jim ()
printf ("program_name: '%s'n", program_name ());
endfunction
printf ("calling jimn")
jim
produces output:
calling jim
program_name: 'joe.m'
But in octave 4.2.1 it gives a warning, and appears to auto-call(!?) jim, and does NOT run top-level immediate code(!?), no output line "calling jim":
warning: function name 'jim' does not agree with function filename '/tmp/joe.m'
program_name: 'joe.m'
Part-2: If I rename same file to "jim.m", then in octave 3.4.4 the output is:
calling jim
program_name: 'jim.m'
in octave 4.2.1 now warning is avoided, but still missing "calling jim" line.
Part-3: With zero functions defined, the top-level code will execute in both versions.
Where are these behaviors (and this change of behavior from version 3 to 4) documented or controlled? Nothing of the sort is mentioned in:
https://octave.org/doc/v4.2.1/Command-Line-Options.html
https://octave.org/doc/v4.2.1/Executable-Octave-Programs.html
How can one write an octave file compatible with both version 3.x and 4.x, or how to invoke 4.x with an extra option to behave compatibly with 3.x? How to execute top-level code in 4.x even when functions are defined?
How can one deterministically know (without trial and error) what function will be auto-called (and with what arguments) in 4.x without documentation of same? This example not enough to nail it down, since there's one and only one function: if there are multiple functions (joe and jim), does the order matter, relative to whether either or none matches the file name?
Note: the shebang (self-contained script) is just a convenience, not relevant to the question, behaviors are same with or without it.
octave
asked 6 hours ago
bk-se
17515
Part-1: In octave 3.4.3 (on centos 6.6) following script file "joe.m":
#!/bin/bash
# for-bash:
#{
exec octave -q --no-init-file "$0" ${1+"$@"}
#}
# for-octave:
function jim ()
printf ("program_name: '%s'n", program_name ());
endfunction
printf ("calling jimn")
jim
produces output:
calling jim
program_name: 'joe.m'
But in octave 4.2.1 it gives a warning, and appears to auto-call(!?) jim, and does NOT run top-level immediate code(!?), no output line "calling jim":
warning: function name 'jim' does not agree with function filename '/tmp/joe.m'
program_name: 'joe.m'
Part-2: If I rename same file to "jim.m", then in octave 3.4.4 the output is:
calling jim
program_name: 'jim.m'
in octave 4.2.1 now warning is avoided, but still missing "calling jim" line.
Part-3: With zero functions defined, the top-level code will execute in both versions.
Where are these behaviors (and this change of behavior from version 3 to 4) documented or controlled? Nothing of the sort is mentioned in:
https://octave.org/doc/v4.2.1/Command-Line-Options.html
https://octave.org/doc/v4.2.1/Executable-Octave-Programs.html
How can one write an octave file compatible with both version 3.x and 4.x, or how to invoke 4.x with an extra option to behave compatibly with 3.x? How to execute top-level code in 4.x even when functions are defined?
How can one deterministically know (without trial and error) what function will be auto-called (and with what arguments) in 4.x without documentation of same? This example not enough to nail it down, since there's one and only one function: if there are multiple functions (joe and jim), does the order matter, relative to whether either or none matches the file name?
Note: the shebang (self-contained script) is just a convenience, not relevant to the question, behaviors are same with or without it.
octave
octave
asked 6 hours ago
bk-se
17515
asked 6 hours ago
bk-se
17515
asked 6 hours ago
bk-se
17515
asked 6 hours ago
bk-se
17515
asked 6 hours ago
bk-se
17515
17515
If the shebang line is not relevant to the question, please remove it. It took me a while to parse that. Let people focus on what is important. See Minimal, Complete, and Verifiable example (especially the minimal part!).
– Cris Luengo
1 hour ago
add a comment |
If the shebang line is not relevant to the question, please remove it. It took me a while to parse that. Let people focus on what is important. See Minimal, Complete, and Verifiable example (especially the minimal part!).
– Cris Luengo
1 hour ago
If the shebang line is not relevant to the question, please remove it. It took me a while to parse that. Let people focus on what is important. See Minimal, Complete, and Verifiable example (especially the minimal part!).
– Cris Luengo
1 hour ago
If the shebang line is not relevant to the question, please remove it. It took me a while to parse that. Let people focus on what is important. See Minimal, Complete, and Verifiable example (especially the minimal part!).
– Cris Luengo
1 hour ago
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
There are different .m file types including (according to Octave 4.2.1):
Functionfiles:
A file that contains definition of one or more functions. The name of a function file often matches the name of the first function defined in the file.
Scriptfiles:
A file that contain lines of code including definition of functions.
Unlike a function file, a script file must not begin with the keyword function . If it does, Octave will assume that it is a function file, and that it defines a single function that should be evaluated as soon as it is defined.
Class definition files.
The behavior of Octave when is executed as:
$octave File
is documented in one of source files (oct-parse.yy) of Octave:
Execute the contents of a script file. For compatibility with Matlab, also execute a function file by calling the function it defines with no arguments and nargout = 0.
Here because your file begins with the keyword function it is considered as a function file so the function jim is automatically called regardless of if you invoke jim or not. So you can remove the expression jim from the end of file and see that the function is automatically called. In version 3.4.3 I think it is assumed as a script file.
To solve the problem you need to add an expression,other than the function keyword, to the beginning of the file to convert it to a script file:
#!/bin/bash
# for-bash:
#{
exec octave -q --no-init-file "$0" ${1+"$@"}
#}
# for-octave:
1;
function jim ()
printf ("program_name: '%s'n", program_name ());
endfunction
printf ("calling jimn")
jim
answered 2 hours ago
rahnema1
9,6902922
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
There are different .m file types including (according to Octave 4.2.1):
Functionfiles:
A file that contains definition of one or more functions. The name of a function file often matches the name of the first function defined in the file.
Scriptfiles:
A file that contain lines of code including definition of functions.
Unlike a function file, a script file must not begin with the keyword function . If it does, Octave will assume that it is a function file, and that it defines a single function that should be evaluated as soon as it is defined.
Class definition files.
The behavior of Octave when is executed as:
$octave File
is documented in one of source files (oct-parse.yy) of Octave:
Execute the contents of a script file. For compatibility with Matlab, also execute a function file by calling the function it defines with no arguments and nargout = 0.
Here because your file begins with the keyword function it is considered as a function file so the function jim is automatically called regardless of if you invoke jim or not. So you can remove the expression jim from the end of file and see that the function is automatically called. In version 3.4.3 I think it is assumed as a script file.
To solve the problem you need to add an expression,other than the function keyword, to the beginning of the file to convert it to a script file:
#!/bin/bash
# for-bash:
#{
exec octave -q --no-init-file "$0" ${1+"$@"}
#}
# for-octave:
1;
function jim ()
printf ("program_name: '%s'n", program_name ());
endfunction
printf ("calling jimn")
jim
answered 2 hours ago
rahnema1
9,6902922
add a comment |
up vote
2
down vote
There are different .m file types including (according to Octave 4.2.1):
Functionfiles:
A file that contains definition of one or more functions. The name of a function file often matches the name of the first function defined in the file.
Scriptfiles:
A file that contain lines of code including definition of functions.
Unlike a function file, a script file must not begin with the keyword function . If it does, Octave will assume that it is a function file, and that it defines a single function that should be evaluated as soon as it is defined.
Class definition files.
The behavior of Octave when is executed as:
$octave File
is documented in one of source files (oct-parse.yy) of Octave:
Execute the contents of a script file. For compatibility with Matlab, also execute a function file by calling the function it defines with no arguments and nargout = 0.
Here because your file begins with the keyword function it is considered as a function file so the function jim is automatically called regardless of if you invoke jim or not. So you can remove the expression jim from the end of file and see that the function is automatically called. In version 3.4.3 I think it is assumed as a script file.
To solve the problem you need to add an expression,other than the function keyword, to the beginning of the file to convert it to a script file:
#!/bin/bash
# for-bash:
#{
exec octave -q --no-init-file "$0" ${1+"$@"}
#}
# for-octave:
1;
function jim ()
printf ("program_name: '%s'n", program_name ());
endfunction
printf ("calling jimn")
jim
answered 2 hours ago
rahnema1
9,6902922
add a comment |
up vote
2
down vote
up vote
2
down vote
There are different .m file types including (according to Octave 4.2.1):
Functionfiles:
A file that contains definition of one or more functions. The name of a function file often matches the name of the first function defined in the file.
Scriptfiles:
A file that contain lines of code including definition of functions.
Unlike a function file, a script file must not begin with the keyword function . If it does, Octave will assume that it is a function file, and that it defines a single function that should be evaluated as soon as it is defined.
Class definition files.
The behavior of Octave when is executed as:
$octave File
is documented in one of source files (oct-parse.yy) of Octave:
Execute the contents of a script file. For compatibility with Matlab, also execute a function file by calling the function it defines with no arguments and nargout = 0.
Here because your file begins with the keyword function it is considered as a function file so the function jim is automatically called regardless of if you invoke jim or not. So you can remove the expression jim from the end of file and see that the function is automatically called. In version 3.4.3 I think it is assumed as a script file.
To solve the problem you need to add an expression,other than the function keyword, to the beginning of the file to convert it to a script file:
#!/bin/bash
# for-bash:
#{
exec octave -q --no-init-file "$0" ${1+"$@"}
#}
# for-octave:
1;
function jim ()
printf ("program_name: '%s'n", program_name ());
endfunction
printf ("calling jimn")
jim
answered 2 hours ago
rahnema1
9,6902922
There are different .m file types including (according to Octave 4.2.1):
Functionfiles:
A file that contains definition of one or more functions. The name of a function file often matches the name of the first function defined in the file.
Scriptfiles:
A file that contain lines of code including definition of functions.
Unlike a function file, a script file must not begin with the keyword function . If it does, Octave will assume that it is a function file, and that it defines a single function that should be evaluated as soon as it is defined.
Class definition files.
The behavior of Octave when is executed as:
$octave File
is documented in one of source files (oct-parse.yy) of Octave:
Execute the contents of a script file. For compatibility with Matlab, also execute a function file by calling the function it defines with no arguments and nargout = 0.
Here because your file begins with the keyword function it is considered as a function file so the function jim is automatically called regardless of if you invoke jim or not. So you can remove the expression jim from the end of file and see that the function is automatically called. In version 3.4.3 I think it is assumed as a script file.
To solve the problem you need to add an expression,other than the function keyword, to the beginning of the file to convert it to a script file:
#!/bin/bash
# for-bash:
#{
exec octave -q --no-init-file "$0" ${1+"$@"}
#}
# for-octave:
1;
function jim ()
printf ("program_name: '%s'n", program_name ());
endfunction
printf ("calling jimn")
jim
answered 2 hours ago
rahnema1
9,6902922
answered 2 hours ago
rahnema1
9,6902922
answered 2 hours ago
rahnema1
9,6902922
answered 2 hours ago
rahnema1
9,6902922
9,6902922
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53371367%2foctave-3-vs-4-script-compatibility-wheres-real-documentation-of-executable-oct%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
If the shebang line is not relevant to the question, please remove it. It took me a while to parse that. Let people focus on what is important. See Minimal, Complete, and Verifiable example (especially the minimal part!).
– Cris Luengo
1 hour ago