[Bug] CallSub and Hard Float Values

Erel,

did find something interesting. When trying to pass a non-variable value via CallSub, get a
Yet, the same thing is ok when calling a code module, or within the same module.

I don't think this was intentional? (worked fine under 2.52)

Ross

It is related to an optimization with CallSub and classes. Generally speaking, the types should be identical when using CallSub. The issue with numeric types conversions will be fixed in the next update.