<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi,<br>
<br>
Le 09/03/2016 01:18, Samuel Gougeon a écrit :<br>
</div>
<blockquote cite="mid:56DF6BCE.8000008@free.fr" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<ul>
<li><tt>warning("stop")</tt>: i agree that, in order to update
all contents and to be sure that results are reliable and not
polluted by unpredictable "[]+-" side effects, this warning
mode will have to be always activated for a very long period,
may be up to Scilab 7. Then, the problem is that this stopping
mode does not resolve the cause: if an up-to-date package
intentionally uses warnings for anything else than []+, it
will be stopped as well. <br>
This warning mode should accept an additional parameter
identifying the type of event (or a series/vector of events)
for which stopping must occur. Shouln't it?</li>
</ul>
</blockquote>
<br>
An other solution could be to implement and use a new <b>warning("trace")
</b>mode, instead of the rough warning("stop").<tt> warning("trace")</tt>
would display a warning + the <tt>where()</tt> or <tt>whereami() </tt>trace
locating where the warning occurs, <i>without stopping the
execution of the script</i>.<br>
This has been proposed while CodeReviewing the implementation of <tt>warning("stop"),</tt>
but has not been retained. Don't know why.<br>
<br>
If the intention of <tt>warning("stop") </tt>(instead of "only <tt>warning("trace"))
</tt>is to urge and compel users to update their codes, then the <tt>oldEmptyBehaviour
flag should not be proposed in the other hand.<br>
<br>
BR<br>
Samuel<br>
<br>
</tt>
</body>
</html>