I see, my confusion came from my habit of naming my .sci files as the
(generaly only) function it contains.
Yet concerning your example I must still be misunderstanding something
as I can't manage to make it work:
- the file test.sci contains only
function this_is_a_very_very_long_function_name()
disp("That''s OK")
endfunction
- then I generate a library by calling genlib as
genlib("testLib","./") // I am in the same directory as test.sci
The file "names" contains indeed "test"
- Then I load the library :
testLib = lib("./")
but this_is_a_very_very_long_function_name() is unknown.
Besides, in the help page of "genlib", it is written that "Scilab
tacitly assumes that file foo.sci defines at least a function named foo"
which is not the case here.
Le 10.07.2015 19:16, Samuel Gougeon a écrit :
Hello,
Le 10/07/2015 10:06, [email protected] a écrit :
.../...
- more important: the long names of my functions are an issue with the
stable version. In particular, "genlib" generated binary files with
full names, and the "names" file contains also the full names of my
functions.
no, of .bin files. Defining
function this_is_a_very_very_long_function_name()
disp("That''s OK")
endfunction
in a file named test.sci
makes genlib() generating test.bin and names containing "test", not
"function this_is_a_very_very_long_function_name".
Then, loading the library with lib(..) is OK:
this_is_a_very_very_long_function_name() is loaded and can be run as
expected.
If you wish to prevent warnings, just enter
warning off
in the console or in your personnal starting file.
HTH
Samuel
_______________________________________________
dev mailing list
[email protected]
http://lists.scilab.org/mailman/listinfo/dev
_______________________________________________
dev mailing list
[email protected]
http://lists.scilab.org/mailman/listinfo/dev
