On 27/01/18 15:06, Adriaan van Os wrote:
C Western wrote:
The following innocuous looking code generates a range check error:
The code shouldn't generate a range check error, as the target type is
signed.
Note that shifting the loop variable to Int64 still triggers the range
check error. Using qword for the loop variable triggers an overflow error.
Apple has never heard of type inclusion or even range checking and is
arbitrarily mixing signed and unsigned types.
I don't think this is an Apple issue - an unsigned type is not
unreasonable for a count.
Colin
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
