linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Steve Graegert <graegerts@gmail.com>
Cc: C programming list <linux-c-programming@vger.kernel.org>
Subject: Re: relationship between standard C and gcc compiler suite?
Date: Wed, 3 Aug 2005 13:22:00 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.63.0508031319220.25465@localhost.localdomain> (raw)
In-Reply-To: <6a00c8d5050803101241bcceb5@mail.gmail.com>

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?

rday

  reply	other threads:[~2005-08-03 17:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-03 13:47 relationship between standard C and gcc compiler suite? Robert P. J. Day
2005-08-03 17:12 ` Steve Graegert
2005-08-03 17:22   ` Robert P. J. Day [this message]
2005-08-03 17:31     ` Steve Graegert
2005-08-04 11:06 ` Glynn Clements

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.63.0508031319220.25465@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=graegerts@gmail.com \
    --cc=linux-c-programming@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).