wayne wrote:
> That sounds like a problem with integers not floating point.
> Yes, YYYYmmDDHHMMSS is too large for a 32-bit integer.
It's an old PHP issue, the mod operator in Wikimedia's #expr
only inherited it.
> I no longer have my copy of IEEE 754 handy to quote, but
> 17 digits is enough for any IEEE 754 complaint system to
> accurately create a double precision rounded correctly to
> the bottom bit and vice versa. Either you are working with
> a non-complaint system, or
...or I confused float and double and long double ;-) In...
<http://meta.wikimedia.org/wiki/Help:Calculation#Accuracy>
...it's still correct, with the relevant links to
<http://en.wikipedia.org/wiki/en:Machine_epsilon> and
<http://www.math.byu.edu/~schow/work/IEEEFloatingPoint.htm>
Sorry for the confusion.
Frank
-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=1007
> That sounds like a problem with integers not floating point.
> Yes, YYYYmmDDHHMMSS is too large for a 32-bit integer.
It's an old PHP issue, the mod operator in Wikimedia's #expr
only inherited it.
> I no longer have my copy of IEEE 754 handy to quote, but
> 17 digits is enough for any IEEE 754 complaint system to
> accurately create a double precision rounded correctly to
> the bottom bit and vice versa. Either you are working with
> a non-complaint system, or
...or I confused float and double and long double ;-) In...
<http://meta.wikimedia.org/wiki/Help:Calculation#Accuracy>
...it's still correct, with the relevant links to
<http://en.wikipedia.org/wiki/en:Machine_epsilon> and
<http://www.math.byu.edu/~schow/work/IEEEFloatingPoint.htm>
Sorry for the confusion.
Frank
-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=1007