Re: Machine epsilon: conclusion

Richard Heathfield wrote:
Richard Tobin said:

In article <ltSdnT3DNLGY9xvbnZ2dnUVZ8tHinZ2d@xxxxxx>,
Richard Heathfield <rjh@xxxxxxxxxxxxxxx> wrote:

#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.

Jacon already described how to suppress this definition if required.

Either it's a standard header (as he claims), or it isn't. If it's a
standard header, it cannot contain QFLT_EPSILON. If it contains
QFLT_EPSILON, it can't be a standard header.

The C99 rationale section 7.1.2 gives an example of how it can, and there is
nothing whatsoever in the standard that contradicts it.
.

Relevant Pages

  • Re: Machine epsilon: conclusion
    ... Richard Heathfield wrote: ... implementation may define QFLT_EPSILON in the standard header ... Jacon already described how to suppress this definition if required. ... in some alphabets" - X3.4, ...
    (comp.lang.c)
  • Re: Machine epsilon: conclusion
    ... Richard Tobin said: ... Jacon already described how to suppress this definition if required. ... Either it's a standard header, ... Richard Heathfield ...
    (comp.lang.c)
  • Re: Machine epsilon: conclusion
    ... Richard Heathfield wrote: ... Jacon already described how to suppress this definition if required. ... Either it's a standard header, ... In any events your argument is specious: Pretty much every compiler ...
    (comp.lang.c)
  • Re: Machine epsilon: conclusion
    ... Richard Tobin said: ... It's a standard header when -ansic is specified, and a non-standard ... Richard Heathfield ...
    (comp.lang.c)
  • Re: Machine epsilon: conclusion
    ... Richard Heathfield wrote: ... implementation may define QFLT_EPSILON in the standard header ... Jacon already described how to suppress this definition if required. ... forbid implementation-defined types. ...
    (comp.lang.c)