Parent document is top of "comp.sys.hp.hpux FAQ"
Previous document is "8.6 How can I tell if something was built debuggable?"
Next document is "8.8 What's the deal with _INCLUDE_xxxx_SOURCE?"

8.7 Is there some kind of problem with using FLT_MIN in ANSI mode?

The C compiler dislikes this construct in ANSI mode:

x = FLT_MIN;    /* <---- warning here */

The problem is that the ANSI mode (_PROTOTYPES) version of FLT_MIN/FLT_MAX in
<float.h> end their constants with an F, which seems to upset the compiler.

The workaround ? Temporarily undef _PROTOTYPES around the <float.h> inclusion:

#ifdef _PROTOTYPES
#undef _PROTOTYPES
#include <float.h>
#define _PROTOTYPES
#else
#include <float.h>
#endif

(Thanks to Richard Lloyd of the Liverpool archive.)

Parent document is top of "comp.sys.hp.hpux FAQ"
Previous document is "8.6 How can I tell if something was built debuggable?"
Next document is "8.8 What's the deal with _INCLUDE_xxxx_SOURCE?"