Stephane,
Thanks for the bugzilla reference, which I was surprised to see as I have
searched there before posting, with search strings like %% but it produced no
results...
This raises my next question: how to seach Bugzilla for "%%" string?
Regards,
Rafael
Le 03/09/2018 à 22:30, Rafael Guerra a écrit :
Dear Scilabers,
Any clues on why the following command totally crashes Scilab 6.0.1 on Win7:
--> printf("A = B ./(C+%%eps) (to avoid division by 0)\n");
while in Scilab 5.5.2 escapes % and outputs properly:
A = B ./(C+%eps) (to avoid
Dipl.-Phys. Klaus Rohe
Adolf-Kolping-Str. 10a
85625 Glonn
Email: klaus-r...@t-online.de
Telefon: +49 (0) 8093 5402
Mobil: +49 (0) 170 8133634
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users
Le 03/09/2018 à 22:30, Rafael Guerra a écrit :
> Dear Scilabers,
>
> Any clues on why the following command totally crashes Scilab 6.0.1 on Win7:
> --> printf("A = B ./(C+%%eps) (to avoid division by 0)\n");
first note that printf is obsolete in scilab-6.0.0 and will be removed
in
On 03.09.2018, at 22:30, Rafael Guerra wrote:
>
> printf("A = B ./(C+%%eps) (to avoid division by 0)\n");
Same on Mac OS X Scilab 6.0.1
Heinz
"Scilb quit unexpectedly"
Process: scilab-bin [985]
Path:
Dear Scilabers,
Any clues on why the following command totally crashes Scilab 6.0.1 on Win7:
--> printf("A = B ./(C+%%eps) (to avoid division by 0)\n");
while in Scilab 5.5.2 escapes % and outputs properly:
A = B ./(C+%eps) (to avoid division by 0)
How to escape % in Scilab 6.0.1's printf?
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
