Re: bitshift of int8, int16, etc?

[Daniel J Sebald]

Daniel J Sebald wrote:

> There are other prefered behaviors for shift.  Say for example the user 
> wants saturation (-127 << 1 => -128 and 126 << 1 => 127) rather than 
> wrap around, which one could use in signal processing.  But that might 
> be a type other than int8.

And in fact, this is the way that the function int8() itself seems to behave:

octave:7> int8(-129)
ans = -128
octave:8> int8(-257)
ans = -128

i.e., saturates rather than wraps.

Dan