<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hello Clément,<br>
<br>
Glad to see that restoring handy profiling facilities is awake.<br>
I am afraid i don't catch all from the SEP. Here is a short list
of remarks that still make me wondering:<br>
<ul>
<li>In 5.5.2, the former functions were about BOTH coverage and
timing. Displaying both informations in the 2 first columns
was very handy.<br>
The current SEP seems to present 2 separated subsets of
functions, as if things are planned to become separated. This
is quite unclear.<br>
<br>
</li>
<li>Reforging things should be a major opportunity to suppress
the splitting in many functions just vs the action.<br>
Hence, the former add_profiling, remove_profiling,
reset_profiling were painfull because inventing, maintaining,
documenting and using 3 separate functions just because of ONE
parameter is changing -- the action -- imo was imo
meaningless. This is a low-level kind of design, whereas
Scilab is a high-level language, the language should be
integrated: I rather expect using<br>
<b>profile(action, target [, options])</b> with for instance
<b>action = "on"|"off"|"reset"|"disp"|"html"</b>|<b>"plot"</b>...<br>
In this way, things are open. If other actions have to be
added latter, the prototype won't change, and no need to have
a Nth function and Nth documentation page in 5 natural
languages.<br>
<br>
</li>
<li>In the SEP, the fact that restoring a display in text mode
in the console is planned does not explicitly appear. Nor the
planned order of columns of results. Both aspects are really
killing details. When improving the code, i never felt the
need of having pleasant colored reports. But, daily, the
display in console was my first and almost only usage.<br>
<br>
</li>
<li>"<span style="color: rgb(0, 0, 0); font-size: 16px;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: 400; letter-spacing:
normal; text-align: left; text-indent: 0px; text-transform:
none; white-space: normal; word-spacing: 0px;
background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial; display: inline !
important; float: none;">instrumentation" is some hardly
understandable devs jargon.</span></li>
</ul>
<p>Best regards</p>
<p>Samuel<br>
</p>
<br>
Le 30/11/2018 à 15:02, Clément David a écrit :<br>
</div>
<blockquote
cite="mid:VI1PR0502MB371099A62147591BD4B75017B0D30@VI1PR0502MB3710.eurprd05.prod.outlook.com"
type="cite">
<pre wrap="">Dear devs,
I started working on re-introducing profiling functions into Scilab 6.0;
these functions will behave very similarly to the Scilab 5 ones but have
been renamed for consistency and their arguments will slightly differs
(macro value vs macro as string). Thanks to Samuel's mail [2], I wrote a SEP
[1] that might finally fix that miss, please comment and give feedbacks !
[1]: <a class="moz-txt-link-freetext" href="https://wiki.scilab.org/SEP%20profiling%20in%20Scilab%206.1">https://wiki.scilab.org/SEP%20profiling%20in%20Scilab%206.1</a>
[2]:
<a class="moz-txt-link-freetext" href="http://mailinglists.scilab.org/New-profiling-module-code-coverage-td4034048">http://mailinglists.scilab.org/New-profiling-module-code-coverage-td4034048</a>.
html
Thanks,
--
Clément
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dev@lists.scilab.org">dev@lists.scilab.org</a>
<a class="moz-txt-link-freetext" href="http://lists.scilab.org/mailman/listinfo/dev">http://lists.scilab.org/mailman/listinfo/dev</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>