That's my whole point Marcus, but the nature of the native floating point
types is something you can get around by implementing your own floating
point type, based on a base-10 system, in the same way that for example
bcmath does it. So my suggestion is; stop using float and double, and make
your o
Hello Ron,
it doesn't matter how accurate your floating or whatever you call it is.
Financial applications require native support which can be realized using
bcmath. Whatever you think besides that - the problem is that any errors
accumulate - that's the nature of float.
If you would like to kn
Yeah, I figured that, but.. changes come as new major PHP releases come.
Maybe this would be something for 5.2/3/4 or 6.0, right? :) Most likely 6.0
I guess. Personally, I just think it's a problem that really should be
tackled when in time PHP6 is to be released. If it isn't done by then,
waiting
Ron Korving wrote:
[...]
Shouldn't PHP abandon the speed of the double in C on this one
[...]
It's not only a matter of speed but also of changing interfaces
to all extensions using doubles (bundled, PECL and 3rd party or
local ones) ...
--
Hartmut Holzgraefe <[EMAIL PROTECTED]>
--
PHP Internals -
Personal recent frustrating float issues made me think of the following...
At the moment apparently the C-type double is used for PHP's float (or
double if you please) storage. I believe it is the philosophy of PHP to make
things easy for its users, and in this perspective I was thinking.. hasn't
