Problem with use of CompareValue
Original Reporter info from Mantis: mftq75
-
Reporter name: C Western
Original Reporter info from Mantis: mftq75
- Reporter name: C Western
Description:
The calls to CompareValue in lcl/maps.pp do not always pick the right function - sometimes an unsigned compare (the version in fpcadds.pp) is called for signed values. This can trigger range check errors. The attached patch explcitly chooses the correct one for each call. I suspect a better solution would be to call the unsigned compare function somethig different (CompareUnsignedValue?)
Mantis conversion info:
- Mantis ID: 8448
- Version: 0.9.21 (SVN)
- Fixed in version: 0.9.23 (SVN)
- Fixed in revision: 10868 (#e1b7c150)
- Target version: 1.0.0
- LazTarget: 1.0