<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Le 05/09/2019 à 12:44, Antoine
Monmayrant a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:80e1e24b-f6e3-92e9-f6a3-01e58e4b7181@laas.fr">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">Le 05/09/2019 à 11:28, Lamy Alain a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:8F232902ADB4E14EB16789FB7006FC847293A8F1@TW-MBX-P01.cnesnet.ad.cnes.fr">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
p.PrformatHTML, li.PrformatHTML, div.PrformatHTML
{mso-style-name:"Préformaté HTML";
mso-style-link:"Préformaté HTML Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
span.PrformatHTMLCar
{mso-style-name:"Préformaté HTML Car";
mso-style-priority:99;
mso-style-link:"Préformaté HTML";
font-family:Consolas;
color:black;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="color:windowtext">What I
didn’t like at first is to use “ones” for a boolean type.
</span></p>
</div>
</blockquote>
That was also my first reaction.<br>
When comparing the learning curve and overall ease of use of
scilab with other options (matlab, julia, python), I always come
to the conclusion that the biggest problem with scilab is the use
of non-intuitive function names.<br>
For example 'horner' for polynom evaluation as compared to
'polyval' is far from obvious unless you are already quite versed
in polynom theory.<br>
</blockquote>
<p><br>
Sincerely, my own learning curve is as steep with "polyval" as
with "horner".<br>
"polyval" means nothing to me (why not the values of
coefficients?), while "eval" does.<br>
And "eval" would be meaningful as well for rationals, as horner,
while polyval would<br>
be just still more puzzling.<br>
</p>
<p>It would be trivial to make eval() working as presently horner()
does, and deprecate (or undocument) horner().<br>
</p>
<blockquote type="cite"
cite="mid:80e1e24b-f6e3-92e9-f6a3-01e58e4b7181@laas.fr"> If you
couple non-intuitive function names (at least for non-specialist
and casual users)<br>
with a documentation that is far from perfect, this scares a lot
of possible users.<br>
</blockquote>
<p>Your actual contributions are welcome and certainly expected.<br>
Things that look obvious for some users that have got some habits
may be rather obscure for all other ones.<br>
<br>
This is why special and open care should be the rule when some new
public symbols (functions, options, etc) are introduced.<br>
</p>
<p>For the time being, this should apply to the forthcoming 6.1.0,
and your constructive criticism is expected about the new
announced (or dark) features, <i>before</i> they are released.<br>
</p>
<p>Best regards<br>
Samuel<br>
<br>
</p>
</body>
</html>