<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>
Thanks for this second version, indeed much clearer to me. This
one brings new questions and comments. <br>
<ul>
<li>The planned ability to target a single function, or a whole
library, or all loaded libraries goes beyond the portage to
Scilab 6. This is already a great improvement.<br>
About possible targets, here are some arising open questions
(they are not requests, just questions for more information) :
<br>
=> Will it be possible to target a user-defined function
out of libraries (defined with deff, function (in console),
exec, jdeff..)?<br>
<br>
</li>
<li><span style="color: rgb(0, 0, 0); font-family: monospace;
font-size: 13px; font-style: normal; font-variant-ligatures:
normal; font-variant-caps: normal; font-weight: 400;
letter-spacing: normal; orphans: 2; text-align: left;
text-indent: 0px; text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px; -webkit-text-stroke-width:
0px; background-color: rgb(255, 255, 255);
text-decoration-style: initial; text-decoration-color:
initial; display: inline !important; float: none;">prof = profileGetInfo()</span>:
the architecture/hierarchy to access to the results is unclear
to me. This is an important point in term of usages. This
point is one of major ones hindering the usage of slint(), as
reported on bugzilla and on users@. It would be a pity to have
the same issue for profiling results. Examples showing how to
address most interesting results would be highly welcome.<br>
</li>
<ul>
<li>Example : How to get totalTime for all functions of a
given library (as a first step to focus on hot functions).<br>
Will it be something like<br>
sel = prof.<span style="color: rgb(0, 0, 0); font-family:
monospace; font-size: 13px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2;
text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255); text-decoration-style: initial;
text-decoration-color: initial; display: inline
!important; float: none;">FunctionTable.ModuleName=="myModule";</span><br>
<span style="color: rgb(0, 0, 0); font-family: monospace;
font-size: 13px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2;
text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255); text-decoration-style: initial;
text-decoration-color: initial; display: inline
!important; float: none;"></span><span style="color:
rgb(0, 0, 0); font-family: monospace; font-size: 13px;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: 400;
letter-spacing: normal; orphans: 2; text-align: left;
text-indent: 0px; text-transform: none; white-space:
normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255); text-decoration-style: initial;
text-decoration-color: initial; display: inline
!important; float: none;">
prof.FunctionTable(sel).FunctionName</span><br>
<span style="color: rgb(0, 0, 0); font-family: monospace;
font-size: 13px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2;
text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255); text-decoration-style: initial;
text-decoration-color: initial; display: inline
!important; float: none;">prof.FunctionTable(sel).TotalTime</span><br>
or like <br>
prof.<span style="color: rgb(0, 0, 0); font-family:
monospace; font-size: 13px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2;
text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255); text-decoration-style: initial;
text-decoration-color: initial; display: inline
!important; float: none;">FunctionTable.<ModuleName>.<FunctionName>.TotalTime<br>
</span>or like<br>
prof.<span style="color: rgb(0, 0, 0); font-family:
monospace; font-size: 13px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2;
text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255); text-decoration-style: initial;
text-decoration-color: initial; display: inline
!important; float: none;">FunctionTable.<FunctionName>.TotalTime</span><br>
prof.<span style="color: rgb(0, 0, 0); font-family:
monospace; font-size: 13px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2;
text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255); text-decoration-style: initial;
text-decoration-color: initial; display: inline
!important; float: none;">FunctionTable.<FunctionName>.ModuleName<br>
<br>
</span></li>
<li>I do not catch why there are 2 distinct 1st level fields <span
style="color: rgb(0, 0, 0); font-family: monospace;
font-size: 13px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2;
text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255); text-decoration-style: initial;
text-decoration-color: initial; display: inline
!important; float: none;">FunctionTable and </span><span
style="color: rgb(0, 0, 0); font-family: monospace;
font-size: 13px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2;
text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255); text-decoration-style: initial;
text-decoration-color: initial; display: inline
!important; float: none;">FunctionCoverage</span>, instead
of having a tenth field <span style="color: rgb(0, 0, 0);
font-family: monospace; font-size: 13px; font-style:
normal; font-variant-ligatures: normal; font-variant-caps:
normal; font-weight: 400; letter-spacing: normal; orphans:
2; text-align: left; text-indent: 0px; text-transform:
none; white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255); text-decoration-style: initial;
text-decoration-color: initial; display: inline
!important; float: none;">FunctionCoverage</span> directly
at the first level. This first level <span style="color:
rgb(0, 0, 0); font-family: monospace; font-size: 13px;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: 400;
letter-spacing: normal; orphans: 2; text-align: left;
text-indent: 0px; text-transform: none; white-space:
normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255); text-decoration-style: initial;
text-decoration-color: initial; display: inline
!important; float: none;">FunctionTable/</span><span
style="color: rgb(0, 0, 0); font-family: monospace;
font-size: 13px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2;
text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255,
255, 255); text-decoration-style: initial;
text-decoration-color: initial; display: inline
!important; float: none;">FunctionCoverage </span>complicates
the addressing, and its motivation is unclear.<br>
<br>
</li>
<li>To me, the most handy first level addressing should be
directly through <functionName>:<br>
<tt>prof.myFun.TotalTime</tt><tt><br>
</tt><tt>prof.myFun.Coverage<br>
etc. This is much simpler and straightforward than with
the syntaxes presented hereabove.</tt><br>
<br>
</li>
<li>About fields names</li>
<ul>
<li>"<span style="color: rgb(0, 0, 0); font-family:
monospace; font-size: 13px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps:
normal; font-weight: 400; letter-spacing: normal;
orphans: 2; text-align: left; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);
text-decoration-style: initial; text-decoration-color:
initial; display: inline !important; float: none;">ModuleName"</span>
might be abbreviated into <span style="color: rgb(0, 0,
0); font-family: monospace; font-size: 13px; font-style:
normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: 400;
letter-spacing: normal; orphans: 2; text-align: left;
text-indent: 0px; text-transform: none; white-space:
normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color:
rgb(255, 255, 255); text-decoration-style: initial;
text-decoration-color: initial; display: inline
!important; float: none;">Module</span> or <tt>Library</tt>
without loss of meaning and clarity. If the expected value
is the name of the library (e.g. <tt>corelib</tt>), then
the field name should be <tt>Library</tt> instead of <tt>Module</tt>
or <tt>ModuleName</tt>. Otherwise, ModuleName will refer
to <tt>core</tt>, not to <tt>corelib</tt>. This would
prevent securely addressing information from the library
(the name of a module is not clearly defined. Is it the
name of its SCI/<module> directory, or the name of
its gateway, or...?<span style="color: rgb(0, 0, 0);
font-family: monospace; font-size: 13px; font-style:
normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: 400;
letter-spacing: normal; orphans: 2; text-align: left;
text-indent: 0px; text-transform: none; white-space:
normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color:
rgb(255, 255, 255); text-decoration-style: initial;
text-decoration-color: initial; display: inline
!important; float: none;"><br>
</span></li>
<li><span style="color: rgb(0, 0, 0); font-family:
monospace; font-size: 13px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps:
normal; font-weight: 400; letter-spacing: normal;
orphans: 2; text-align: left; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);
text-decoration-style: initial; text-decoration-color:
initial; display: inline !important; float: none;">"FirstLine"
: is it the "Prototype"?</span></li>
<li><span style="color: rgb(0, 0, 0); font-family:
monospace; font-size: 13px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps:
normal; font-weight: 400; letter-spacing: normal;
orphans: 2; text-align: left; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);
text-decoration-style: initial; text-decoration-color:
initial; display: inline !important; float: none;">InstructionsCount,
BranchesCount, PathsCount</span> : <br>
</li>
<ul>
<li>these fields would be new results, not available in
Scilab 5<span style="color: rgb(0, 0, 0); font-family:
monospace; font-size: 13px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps:
normal; font-weight: 400; letter-spacing: normal;
orphans: 2; text-align: left; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);
text-decoration-style: initial; text-decoration-color:
initial; display: inline !important; float: none;">.</span>
For the time being, I do not understand what they
represent nor what they can be used to<span
style="color: rgb(0, 0, 0); font-family: monospace;
font-size: 13px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps:
normal; font-weight: 400; letter-spacing: normal;
orphans: 2; text-align: left; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);
text-decoration-style: initial; text-decoration-color:
initial; display: inline !important; float: none;">.</span></li>
<li>Does "executed lines count" stand for only lines that
are actually executed, or does it stand for <u>all</u>
lines, with a count 0 for not executed ones?<span
style="color: rgb(0, 0, 0); font-family: Arial,
"Lucida Grande", sans-serif; font-size:
16px; font-style: normal; font-variant-ligatures:
normal; font-variant-caps: normal; font-weight: 400;
letter-spacing: normal; orphans: 2; text-align: left;
text-indent: 0px; text-transform: none; white-space:
normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color:
rgb(255, 255, 255); text-decoration-style: initial;
text-decoration-color: initial; display: inline
!important; float: none;"><br>
<br>
</span></li>
</ul>
</ul>
</ul>
<li>The case of <b>nested functions</b> (a function defined in
a function, etc) is not presented. There were some issues in
Scilab 5 about them. See for instance the <a
href="http://bugzilla.scilab.org/show_bug.cgi?id=12104">bug
12104</a> or the <a
href="http://bugzilla.scilab.org/show_bug.cgi?id=12105">bug
12105</a>.<br>
<br>
</li>
<li>The case of <b>internal functions defined in the same .sci
file </b>after the main function is not presented. This is
a new topic, since the Scilab 6 processing is new with respect
to these local dependencies. Will profiling these internal
dependencies be possible?<br>
<br>
</li>
<li><i>"</i><span style="mso-fareast-language:EN-US"
lang="EN-US"><i>The main issue with switching API is the
associated effort to port existing Scilab 5 toolset to the
new API. As you propose, a Matlab-like `profile` might be
a later extension."</i><br>
I am sorry, i do not clearly understand this point. Anyway,
the API is changed, since functions are renamed, and the
format of results is completely changed.<br>
Writting a profile() macro routing to the internal
profileEnable() etc would be somehow let's say ~3% of the
time, by far the easiest part of the forge, compared to the
implementation/rewritting of hard code. But it would ease
usages and maintenance and documentation. Skipping it looks
like a bit self censorship, self limiting impact of a great
work.<br>
At least, not splitting the documentation in N separated
pages, but building a single help page presenting all
profiling functions and usages would be better.<br>
</span></li>
</ul>
<p>Thanks again for all your efforts and work.<br>
<br>
Best regards<br>
Samuel<br>
</p>
Le 03/12/2018 à 16:31, Clément David a écrit :<br>
</div>
<blockquote
cite="mid:AM6PR0502MB3702446309FF22C1BD81FF79B0AE0@AM6PR0502MB3702.eurprd05.prod.outlook.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EmailStyle22
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:611670105;
mso-list-template-ids:1024915216;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="mso-fareast-language:EN-US"
lang="EN-US">Hello Samuel and thanks for your comments,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">I updated the SEP with more information
clarifying some aspects. These `profile` functions are not
supposed to replace the existing `coverage` ones. The
underlying execution counters are re-used for the two
implementations but the usage might slightly be different:
produce a static report for the coverage or display
performance information while developing. I reword some
aspect to clarify the display and show methods, the
“instrumentation”<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">At first, I want to map the Scilab 5 features
before trying to push enhancement or API modification so I
used similar names as in Scilab 5. The main issue with
switching API is the associated effort to port existing
Scilab 5 toolset to the new API. As you propose, a
Matlab-like `profile` might be a later extension.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">--<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">Clément<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span
lang="EN-US"> dev <a class="moz-txt-link-rfc2396E" href="mailto:dev-bounces@lists.scilab.org"><dev-bounces@lists.scilab.org></a> <b>On
Behalf Of </b>Samuel Gougeon<br>
<b>Sent:</b> Sunday, December 2, <u>2018</u> 8:54 PM<br>
<b>To:</b> List dedicated to the development of Scilab
<a class="moz-txt-link-rfc2396E" href="mailto:dev@lists.scilab.org"><dev@lists.scilab.org></a><br>
<b>Subject:</b> Re: [Scilab-Dev] SEP advanced
function/profiling in Scilab 6<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hello Clément,<br>
<br>
Glad to see that restoring handy profiling facilities is
awake.<br>
I am afraid <u>i</u> don't catch all from the SEP. Here is
a short list of remarks that still make me <u>wondering</u>:<o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l0
level1 lfo1">In 5.5.2, the former functions were about
BOTH coverage and timing. Displaying both <u>informations</u>
in the 2 first columns was very handy.<br>
The current SEP seems to present 2 separated subsets of <u>functions,</u>
as if things are planned to become separated. This is
quite unclear.<o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l0
level1 lfo1">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 <u>painfull</u> because inventing,
maintaining, documenting and using 3 separate functions
just because of ONE parameter is changing -- the action --
<u>imo</u> was <u>imo</u> 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 <u>latter</u>, the prototype won't change, and no
need to have <u>a Nth</u> function and Nth documentation
page in 5 natural languages.<o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l0
level1 lfo1">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.<o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1">"<span
style="font-size:12.0pt;background:white">instrumentation"
is some hardly understandable devs jargon.</span><o:p></o:p></li>
</ul>
<p>Best regards<o:p></o:p></p>
<p>Samuel<o:p></o:p></p>
<p class="MsoNormal"><br>
Le 30/11/2018 à 15:02, Clément David a écrit :<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Dear devs,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I started working on re-introducing profiling functions into Scilab 6.0;<o:p></o:p></pre>
<pre>these functions will behave very similarly to the Scilab 5 ones but have<o:p></o:p></pre>
<pre>been renamed for consistency and their arguments will slightly differs<o:p></o:p></pre>
<pre>(macro value vs macro as string). Thanks to Samuel's mail [2], I wrote a SEP<o:p></o:p></pre>
<pre>[1] that might finally fix that miss, please comment and give feedbacks !<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>[1]: <a moz-do-not-send="true" href="https://wiki.scilab.org/SEP%20profiling%20in%20Scilab%206.1">https://wiki.scilab.org/SEP%20profiling%20in%20Scilab%206.1</a><o:p></o:p></pre>
<pre>[2]:<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://mailinglists.scilab.org/New-profiling-module-code-coverage-td4034048">http://mailinglists.scilab.org/New-profiling-module-code-coverage-td4034048</a>.<o:p></o:p></pre>
<pre>html<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thanks,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>--<o:p></o:p></pre>
<pre>Clément<o:p></o:p></pre>
<p class="MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>dev mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:dev@lists.scilab.org">dev@lists.scilab.org</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://lists.scilab.org/mailman/listinfo/dev">http://lists.scilab.org/mailman/listinfo/dev</a><o:p></o:p></pre>
</blockquote>
<p><o:p> </o:p></p>
</div>
<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>