Re: Machine epsilon: conclusion
- From: Richard Heathfield <rjh@xxxxxxxxxxxxxxx>
- Date: Sat, 30 Jun 2007 19:51:31 +0000
jacob navia said:
Richard Heathfield wrote:
jacob navia said:
<snip>
For the different representations we have in the standard header
<float.h>:
#define FLT_EPSILON 1.19209290e-07F // float
#define DBL_EPSILON 2.2204460492503131e-16 // double
#define LDBL_EPSILON 1.084202172485504434007452e-19L //long double
// qfloat epsilon truncated so that it fits in this page...
#define QFLT_EPSILON 1.09003771904865842969737513593110651 ... E-106
You have the same bug as last time. No standard-conforming
implementation may define QFLT_EPSILON in the standard header
<float.h>, as I pointed out to you earlier this week.
I have told you thousand times that this can be disabled
by using -ansic.
You don't seem to understand my point, which is that you are describing
<float.h> as a *standard header*, and yet you *also* describe it as
containing QFLT_EPSILON. It can't *both* be a standard header *and*
contain QFLT_EPSILON at the same time. If it is a standard header, it
does not contain QFLT_EPSILON. If it contains QFLT_EPSILON, it is not a
standard header. Your claim that QFLT_EPSILON is in a standard header
is simply wrong, switch or no switch.
--
Richard Heathfield <http://www.cpax.org.uk>
Email: -www. +rjh@
Google users: <http://www.cpax.org.uk/prg/writings/googly.php>
"Usenet is a strange place" - dmr 29 July 1999
.
- Follow-Ups:
- Re: Machine epsilon: conclusion
- From: Flash Gordon
- Re: Machine epsilon: conclusion
- From: jacob navia
- Re: Machine epsilon: conclusion
- References:
- Machine epsilon: conclusion
- From: jacob navia
- Re: Machine epsilon: conclusion
- From: Richard Heathfield
- Re: Machine epsilon: conclusion
- From: jacob navia
- Machine epsilon: conclusion
- Prev by Date: Re: Machine epsilon: conclusion
- Next by Date: Re: Machine epsilon: conclusion
- Previous by thread: Re: Machine epsilon: conclusion
- Next by thread: Re: Machine epsilon: conclusion
- Index(es):
Relevant Pages
|