<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hello,<br>
<br>
Le 01/12/2015 12:11, francois.granade a écrit :<br>
</div>
<blockquote
cite="mid:5395ECC5-F84B-4773-AD21-B8E9EBD313DF@scilab-enterprises.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Good catch, the release notes are not very clear :)
<div><br>
</div>
<div>There *is* some basic documentation, however, in the change
log (accessible from "edit SCI/CHANGES_6.0.X" for example).
Pasting them:</div>
<div><br>
</div>
<div>
<div style="margin: 0px; font-size: 9px; font-family: Menlo;">New
Features</div>
<div style="margin: 0px; font-size: 9px; font-family: Menlo;">============</div>
<div style="margin: 0px; font-size: 9px; font-family: Menlo;
min-height: 10px;"><br>
</div>
<div style="margin: 0px; font-size: 9px; font-family: Menlo;">*
Scilab now includes a full-featured debugger, with ability to
run Scilab scripts or functions step-by-step, to put
(conditional) breakpoint, in particular break only when an
exception is set. Run <span style="color: #af3782">"help
debug"</span> for more information.</div>
<div style="margin: 0px; font-size: 9px; font-family: Menlo;
min-height: 10px;"><br>
</div>
<div style="margin: 0px; font-size: 9px; font-family: Menlo;">*
A new profiler and coverage tool has been added.</div>
<div style="margin: 0px; font-size: 9px; font-family: Menlo;">
It replaces the <span style="color: #af3782">"profile"</span>
function (which is still there but not working, and will be
removed in the final release)<span style="color: #7c7ca6"><b>.</b></span></div>
<div style="margin: 0px; font-size: 9px; font-family: Menlo;">
It produces HTML report for the time spent (profile) on each
line. Example of use:</div>
<div style="margin: 0px; font-size: 9px; font-family: Menlo;
min-height: 10px;"><br>
</div>
<div style="margin: 0px; font-size: 9px; font-family: Menlo;">
covStart(isempty) // instruments the <span style="color:
#af3782">"isempty"</span> macro; instrumenting a whole
library can be done with: covStart(<span style="color:
#af3782">"elementary_functions"</span>)</div>
<div style="margin: 0px; font-size: 9px; font-family: Menlo;">
for i=1:1e5; isempty(i); end // execute some code - this
will be profiled</div>
<div style="margin: 0px; font-size: 9px; font-family: Menlo;">
covWrite(<span style="color: #af3782">"html"</span>, <span
style="color: #af3782">"TMPDIR/coverage"</span>) // write
the profiling/coverage report as <span style="color: #af3782">"report.html"</span>
in the folder specified as second parameter</div>
<div style="margin: 0px; font-size: 9px; font-family: Menlo;">
covStop(); // stop the profiling</div>
<div style="margin: 0px; font-size: 9px; font-family: Menlo;
min-height: 10px;"><br>
</div>
<div style="margin: 0px; font-size: 9px; font-family: Menlo;">
A function to merge multiple profiler/coverage is provided
too: covMerge([ list_of_files_to_merge], file_to_merge_to)<span
style="color: #7c7ca6"><b>.</b></span></div>
<div style="margin: 0px; font-size: 9px; font-family: Menlo;">
The API will change before the release; the current API is
mostly to get feedback from the community.</div>
<div style="margin: 0px; font-size: 9px; font-family: Menlo;
min-height: 10px;"><br>
</div>
<div style="margin: 0px; font-size: 9px; font-family: Menlo;">*
A <span style="color: #af3782">"lint"</span>-like command,
slint, has been added, for code static analysis: it detects
unclear, risky or suspicious code.</div>
<div style="margin: 0px; font-size: 9px; font-family: Menlo;">
Usage: slint(<span style="color: #af3782">"<sci
filename>"</span>)<span style="color: #7c7ca6"><b>.</b></span>
It is not documented yet.</div>
<div style="margin: 0px; font-size: 9px; font-family: Menlo;
min-height: 10px;"><br>
</div>
<div><br>
</div>
<div>We didn't want to advertise it too much, as we may changes
these functions before the release...</div>
</div>
</blockquote>
<br>
Here we are on the dev@ list. If even on the dev@ it is not possible
to openly discuss about features <i>in development</i>, then where?<br>
<br>
This part of the release notes is very surprising, because it only
and hardly starts what could be a proper Scilab Enhancement
Proposal. <br>
No SEP was published. This means, that, no, you don't really need
our feedback, since SEP are mostly designed for that.<br>
For the moment, "coverage" does not look at all as a new functional
feature.<br>
Among the 3 proposed syntaxes, the first one is (now?) bugged:<br>
covStart(isempty) // yielded an error the first time i ran it.
And when i tried<br>
covStart("isempty") // it did not complain. After that, i tried
again, from another fresh session, or a running one, <br>
covStart(isempty) // and it did no longer complain. May be it
will complain again later, who knows.<br>
<br>
Mixing input types between strings (name of functions or here
library) and functions pointers (covStart(isempty), but
covStart("mylibrary")) were already misleading within the former set
of profiling functions. This has been reported on bugzilla. The
first announcement of the new set shows that we learn almost nothing
about former design/usage complications.<br>
<br>
Then i tried with covStart("strsubst") // that is a builtin. Are
built-in profilable? I know that the former profiling applied "only"
on Scilab macros, but since this is a new profiler, i do not assume
anything about any possible restriction. I do not really expect any
answer here. A SEP is the right place to define what does a
function, with which kind of parameters, according to which
parameters format (string or function or primitive), the naming,
etc. A SEP is also a very good start to build the related
documentation.<br>
<br>
Whatever "strsubst" is an acceptable entry or not, no error is
produced.<br>
<br>
After running "uman" that uses a lot of strsubst(), covWrite(..)
produces an empty report (attached).<br>
Same thing with covStart(strsubst)<br>
Same thing with covStart(uman) or covStart("uman") // that is a
macro<br>
Nothing. I get nothing with the beta-1. Unfortunately, i have
uninstalled the alpha-2 for which these "coverage" functions have
been first announced. The announcement has not changed for the
beta-1.<br>
<br>
The former profiling functions had an output in console, as well as
in argout to enable post-processing (as for the running upgrade of
bench_run(), >10 (?) years after its first release) , or in an
interactive plot.<br>
The few that is announced for the new profiling features looks much
less than what was formerly available.<br>
<br>
So, as somewhat Antoine told it, and after your answer, what i
understand is that S/E needs to tell that it needs our feedback. I
guess that we are expected to believe it. For the moment nothing
really tell us that it needs more than telling it. But this can
change.<br>
<br>
Thanks, and regards.<br>
<br>
Samuel Gougeon<br>
One of your 100000 industrial downloaders/month<br>
<br>
</body>
</html>