Thank you Serge.
If I understood you correctly, it is not possible then to have a small range, e.g, 1..100, use a DWORD.
If I understood you correctly, it is not possible then to have a small range, e.g, 1..100, use a DWORD. It will use the smallest type that can encompass the range (in that case, byte.)Yes. Moreover, even with large boundaries, it may be unreliable, because it is not specified in the documentation.
Did I get it right ?
Is there some way of defining the range to have the compiler consider it a DWORD ?The FPC is very reluctant to make reservations for memory that will, per definition, always stay zero. A possible workaround is to wrap your range in a record: