Hello,
I would like to point out the conventions used by Scilab and Matlab when
an integer number is subject to overflow:
Scilab 6.0.1:
--> uint8(255)+1
ans =
0
Matlab R2017b
>> uint8(255)+1
ans =
uint8
255
Do you see any reason in favor of one of each ?
S.
--
Stéphane Mott
Le 23/02/2018 à 13:45, Stéphane Mottelet a écrit :
Hello,
I would like to point out the conventions used by Scilab and Matlab
when an integer number is subject to overflow:
Scilab 6.0.1:
--> uint8(255)+1
ans =
0
Matlab R2017b
>> uint8(255)+1
ans =
uint8
255
Do you see any rea
See some advantages of saturation overflow in article:
https://en.wikipedia.org/wiki/Saturation_arithmetic
-Original Message-
From: users [mailto:users-boun...@lists.scilab.org] On Behalf Of Stéphane
Mottelet
Sent: Friday, February 23, 2018 2:06 PM
To: International users mailing list f
Le 23/02/2018 à 14:06, Stéphane Mottelet a écrit :
Le 23/02/2018 à 13:45, Stéphane Mottelet a écrit :
Hello,
I would like to point out the conventions used by Scilab and Matlab
when an integer number is subject to overflow:
Scilab 6.0.1:
--> uint8(255)+1
ans =
0
Matlab R2017b
>> uint
Le 23/02/2018 à 15:50, Samuel Gougeon a écrit :
Le 23/02/2018 à 14:06, Stéphane Mottelet a écrit :
Le 23/02/2018 à 13:45, Stéphane Mottelet a écrit :
Hello,
I would like to point out the conventions used by Scilab and Matlab
when an integer number is subject to overflow:
Scilab 6.0.1:
-->
Thank you,
I loaded IPCV.
When I tried to execute a program from a gui screen, scilab 6.01 stopped
working.
I will have to see whats wrong.
Regards
Offer
From: users [mailto:users-boun...@lists.scilab.org] On Behalf Of Claus Futtrup
Sent: Thursday, February 22, 2018 8:26 PM
To: Users mail
