Re: Machine epsilon: conclusion


"Richard Tobin" <richard@xxxxxxxxxxxxxxx> ha scritto nel messaggio news:f65rv2$14u7$1@xxxxxxxxxxxxxxxxxxxxxxxxxx
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.

Couldn't simplily he call it _QFLT_EPSILON? The standard doesn't
forbid implementation-defined types.


.

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 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: ... 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 Heathfield wrote: ... // qfloat epsilon truncated so that it fits in this page... ... implementation may define QFLT_EPSILON in the standard header, as I pointed out to you earlier this week. ...
    (comp.lang.c)