Makes perfect sense, thanks for the quick answer :-)
Florian Klaempfl wrote:
Ror/rol are very sensitive against data type changes so this ensures you
get always the desired result. While x shr 1 has the same result if the
value fits in x, ror(x,1) has different results if x is a byte, word or
dw
Michael Green schrieb:
> Quick question: Is there any particular reason why the system function
> ror() (in /fpc/rtl/inc/systemh.inc) has been divided up into rorbyte,
> rordword and rorqword (and respectively for rol() ) instead of being
> overloaded?
Ror/rol are very sensitive against data type
