floats are implemented in various way, one is, as the name says, with a floating point. So there is a number , like 134523, and a point index, eg. 4, the result would then be 1345.23 cause the point has to be set after the forth digit.
A binary piece of ram (eg 32 bits) would then use eg. 5 bits to store the point position and the rest for the value without a point.
thought my question was clear. when there is a float in the ram, and you peek it as an int, that's the binary integer equivalent of the float. I needed this because when you peek random ram adresses as float, blitz will oftenly return NAN (not a number), and when you compare this with eg. zero, it will say NAN is zero, although it may be something completely diffrent that simply was not a float. So I needed to compare in a binary way (see the "how to hack properties" thread in the tutorials section).
A binary piece of ram (eg 32 bits) would then use eg. 5 bits to store the point position and the rest for the value without a point.
thought my question was clear. when there is a float in the ram, and you peek it as an int, that's the binary integer equivalent of the float. I needed this because when you peek random ram adresses as float, blitz will oftenly return NAN (not a number), and when you compare this with eg. zero, it will say NAN is zero, although it may be something completely diffrent that simply was not a float. So I needed to compare in a binary way (see the "how to hack properties" thread in the tutorials section).