From: merlyn@stonehenge•com (Randal L. Schwartz)
To: Jason Riedy <ejr@EECS•Berkeley.EDU>
Cc: git@vger•kernel.org
Subject: Re: [PATCH] Use inttypes.h rather than stdint.h.
Date: Thu, 25 Jan 2007 13:54:32 -0800 [thread overview]
Message-ID: <868xfqrcvb.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <24182.1169759500@lotus.CS.Berkeley.EDU> (Jason Riedy's message of "Thu, 25 Jan 2007 13:11:40 -0800")
>>>>> "Jason" == Jason Riedy <ejr@EECS•Berkeley.EDU> writes:
Jason> Older Solaris machines lack stdint.h but have inttypes.h.
Jason> The standard has inttypes.h including stdint.h, so at worst
Jason> this pollutes the namespace a bit.
Heh... I just ran into this for $client. Nice.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge•com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2007-01-25 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 21:11 [PATCH] Use inttypes.h rather than stdint.h Jason Riedy
2007-01-25 21:54 ` Randal L. Schwartz [this message]
2007-01-26 6:55 ` Simon 'corecode' Schubert
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=868xfqrcvb.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge$(echo .)com \
--cc=ejr@EECS$(echo .)Berkeley.EDU \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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