On 8/3/05, Robert P. J. Day <[EMAIL PROTECTED]> wrote:
> On Wed, 3 Aug 2005, Steve Graegert wrote:
>
> > In case of GCC, including <stdbool.h> cleans up #defines and allows
> > C++ compilation. It is therefore recommended to #define these
> > identifiers only when _needed_ and after including <stdbool.h>.
> > <stdbool.h> is provided as an extension and, for this reason, not
> > placed into the include directory of the C standard library.
>
> ok, this is where i might be having my difficulty. in H&S (5th ed),
> p. 325, i read (emphasis added):
>
> "Certain Standard C libraries can be considered part of the language.
> The provide standard definitions and parameterization that help make C
> programs more portable... These core libraries consist of the header
> files ... stdbool.h, ..."
>
> my reading of this is that stdbool.h is not an extension, it's a part
> of the core. what am i mnisreading here?
It is not an extension to the standard, namely C99, but an extension
of GCC in order to allow native C code to be compiled as C++ in a
clean way. So you're reading was absolutely correct. Almost every
vendor ships with <stdbool.h>, sometimes it is placed in the include
directory for the compiler (on Linux/GNU systems at least), but HP,
for example, puts it in /usr/include. It's just a Linux thing to put
it elsewhere.
Regards
\Steve
--
Steve Graegert <[EMAIL PROTECTED]>
Software Consultancy {C/C++ && Java && .NET}
Mobile: +49 (176) 21248869
Office: +49 (9131) 7126409
-
To unsubscribe from this list: send the line "unsubscribe linux-c-programming"
in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
