From: "Robert P. J. Day" <rpjday@mindspring.com>
To: "Smith, Jason - VA" <JasonSmith@verisign.com>
Cc: C programming list <linux-c-programming@vger.kernel.org>
Subject: RE: the rationale for defining macros for simple types?
Date: Thu, 10 Aug 2006 11:45:58 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0608101142570.17196@localhost.localdomain> (raw)
In-Reply-To: <C9D203A88CE285489324AEDC5174158604CEB983@dul1wnexmb01.vcorp.ad.vrsn.com>
On Thu, 10 Aug 2006, Smith, Jason - VA wrote:
> Robert,
>
> stdint.h is a part of glibc methinks, and not part of any blessed
> standard that I am aware of.
my copy of harbison and steele lists <stdint.h> as part of C99. am i
somehow reading that incorrectly?
> What you probably want to include for the int*_t types is
> <inttypes.h>, which found in /usr/(local/)?/include on most of the
> common *nix's out there (might be part of a standard like C99 too).
again, from my copy of H&S, inttypes.h includes stdint.h, so i guess
either one would work fine. i'm guessing inttypes.h would be the
better choice since it's more all-encompassing. thanks.
rday
next prev parent reply other threads:[~2006-08-10 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 15:35 the rationale for defining macros for simple types? Smith, Jason - VA
2006-08-10 15:45 ` Robert P. J. Day [this message]
2006-08-10 16:06 ` Robert P. J. Day
-- strict thread matches above, loose matches on Subject: below --
2006-08-10 11:58 Robert P. J. Day
2006-08-10 20:57 ` 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.64.0608101142570.17196@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=JasonSmith@verisign.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).