My personal stupid approach is to get rid from float completely, and use only integer/longinteger in any calculation needed.That doesn't sound stupid, as opposed to write a floating point emulation code, which in the end will still be slow. I think what the .NET runtime does is exactly just that when it detects a processor without floating point support.
Absolutely. That was what I worry about: compiler's emulation (of unsupported floating point by processor) will drops the performance again.My personal stupid approach is to get rid from float completely, and use only integer/longinteger in any calculation needed.That doesn't sound stupid, as opposed to write a floating point emulation code, which in the end will still be slow. I think what the .NET runtime does is exactly just that when it detects a processor without floating point support.
@avra, god bless you of your kind let us know that great pascal units ( plus quickly updating broken link).You're most welcome. I thank you for your kind words.
So, @avra, by using AFP/Fix.pas, we only have one chance to decide the range of integer~fraction part per application, right?No, you can change it programatically whenever you want. In "FixedPointMath.pas" example for E-Lab AvrCo Pascal you can see this line: