<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Le 15/07/2015 13:24, Antoine ELIAS a
écrit :<br>
</div>
<blockquote cite="mid:55A642F4.8000009@scilab-enterprises.com"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">.../...<br>
Scilab 6, no more create "names" file.<br>
New "lib" file ( xml format, it is readable ) contains all
needed information.<br>
</div>
</blockquote>
.<br>
Why not renaming it lib.xml? <br>
1) This would better show its format, and -- overall -- <br>
2) this would allow to distribute modules containing only macros
under a <b>single version</b> compatible with <b>both</b> 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.<br>
<br>
Example: for the module <a class="moz-txt-link-freetext" href="http://atoms.scilab.org/toolboxes/uman">http://atoms.scilab.org/toolboxes/uman</a>, 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.<br>
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.<br>
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.<br>
<br>
Samuel<br>
<br>
</body>
</html>