At runtime there are no identical numbers unless both are defined at const, which makes the comparision pointless as you know the result upfront.
If you compare floats, always compare with an epsilon margin within they must be the same or do not use floating point bug fixed point math or something similar.
One thing that will cause further problems if you convert code it, which was mentioned by skid, is that the "old blitz" round the output result, so you don't have full float accuracy. On the other side, this behavior allows float = float checks up to a given point (around .001 - .005 accuracy with "normal" numbers *0 - 1000*)
If you compare floats, always compare with an epsilon margin within they must be the same or do not use floating point bug fixed point math or something similar.
One thing that will cause further problems if you convert code it, which was mentioned by skid, is that the "old blitz" round the output result, so you don't have full float accuracy. On the other side, this behavior allows float = float checks up to a given point (around .001 - .005 accuracy with "normal" numbers *0 - 1000*)