José Manuel Berenguer

Any ideas about why in Max x >> y != 0, not only for y = 0 but also for any y in {64, 128, 192, 256, ... } , even when y is greater than the number of bits of x binary codification ? 

For instance, it happens that, x >> y = x when y is in {0, 64, 128, 192, 256, ... } , for any x < 255 ...

This yields unexpected results in jit,op when operatig with char matrices ...

Any ideas about why in Max  x >> y != 0, not only for y = 0 but also for any y in {64, 128, 192, 256, ... } , even when y is  greater than the number of bits of x binary codification ? 
For instance, it happens that,   x >> y = x  when y is in {0, 64, 128, 192, 256, ... } , for any x < 255 ... 

This yields unexpected results  in jit,op when operatig with char matrices ...

Any ideas about why in Max  x >> y != 0, not only for y = 0 but also for any y in {64, 128, 192, 256, ... } , even when y is  greater than t

Weird behavior of [[ >> ]]