Le 03/09/2018 à 12:38, amonm...@laas.fr a écrit :
> Hello,
>
> As a workaround, if you replace
> 1!=0 // syntax error
> with
> str="1!=0";
> evstr(str);
> it seems to work as you expected.
Yes the bug disappear with execstr ? In fact my example wasn't clear
enough, here is a better
Hello,
As a workaround, if you replace
1!=0 // syntax error
with
str="1!=0";
evstr(str);
it seems to work as you expected.
Anyway, I think the try/catch structure can catch errors occurring at
runtime (like division by zero, etc ...), but not syntax errors.
You are supposed to
Hi,
In scilab-5 I used to save console output of script file execution in a
text file with "diary", this seems to fail in scilab-6, for new errors
types recently added (Syntax error, Unexpected token ). Perhaps I
misunderstood something in try/catch statement , let's consider the file
