[Scilab-Dev] lib() unavailable on YaSp?

Samuel Gougeon sgougeon at free.fr
Wed Jul 15 14:35:37 CEST 2015


Le 15/07/2015 13:24, Antoine ELIAS a écrit :
> .../...
> Scilab 6, no more create "names" file.
> New "lib" file ( xml format, it is readable ) contains all needed 
> information.
.
Why not renaming it lib.xml?
1) This would better show its format, and -- overall --
2) this would allow to distribute modules containing only macros under a 
*single version* compatible with *both* Scilab 5 and Scilab 6 (including 
both {"lib" and "names"} and "lib.xml" files), since .bin contents are 
unchanged: .bin generated with YaSp look OK for Scilab 5, and conversely.

Example: for the module http://atoms.scilab.org/toolboxes/uman, the 
supported Scilab version is set to "any" in order to see the (same 
version of the) module in ATOMS in Scilab 5 as well as in Scilab 6.
But with the present "lib" coming from Scilab 5, the module does not 
load at Scilab 6 startup (error). If i replace it with the "lib" file 
got from YaSp, the module won't load with Scilab 5.
If the "lib" file from Scilab 6 was renamed "lib.xml", it would not be 
necessary to create a new version of "uman" specific to Scilab 6: adding 
"lib.xml" to "~\macros\" would be enough, and in the still long expected 
meantime from Scilab 5.5 to the official Scilab 6 (may be still 2 years, 
for all the alphas and betas...?), the same and only version will be OK, 
without having to maintain two versions for their parallel fixes and 
upgrades.

Samuel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/dev/attachments/20150715/bf47d6e4/attachment.htm>


More information about the dev mailing list