Closed ollydev closed 5 years ago
Does this actually solve the out of range errors, because it's still mixing signed and unsigned integers?
@nielsAD This is what is happening but at runtime:
with i
being FCodePointers[i]^
which is SizeUInt
Yeah this PR is bogus, it does fix it though but I think FPC is just being weird.
Maybe we should just disable rangechecks in this function.
To add to this, this only happens with a empty script. But i'm going to close this for now.
In the future ideally all the
Integer
related to byte code should be replaced withTCodePos
orTCodeOffset
.