Hello fredvs, you wrote on Tue, 10 Mar 2020 12:52:22 -0700 (MST):
> Hello Roland. > > Doing this: > > const > foldhiddenbit = 7; > foldhiddenmask = byte(1) shl foldhiddenbit; > currentfoldhiddenbit = 6; > currentfoldhiddenmask = byte(1) shl currentfoldhiddenbit; > foldlevelmask = byte(not (foldhiddenmask or currentfoldhiddenmask)); > foldissumbit = 0; > foldissummask = $01; > rowstatemask = $7f; > > Makes the compiler happy but the warning is still there and point to : > > ---> foldlevelmask = byte(not (foldhiddenmask or > currentfoldhiddenmask)); > > msedatalist.pas(891,18) Warning: range check error while evaluating > constants (-193 must be between 0 and 255) Does that new fpc version implement (and differentiate between) _signed_ and _unsigned_ byte size values now? This looks a whole lot like similar warnings issued by C compilers when you mix signed and unsigned "char"s. This might even apply to subranges of bytes, like with C with bit field values, which can also have signedness... (In shoert, a mess.) -- -- (Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem) ----------------------------------------------------------- Mit freundlichen Grüßen, S. Schicktanz ----------------------------------------------------------- _______________________________________________ mseide-msegui-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
