git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Use inttypes.h rather than stdint.h.

From
Randal L. Schwartz <merlyn@stonehenge.com>
Date
Jan 25, 2007, 21:54 UTC
Message-ID
<868xfqrcvb.fsf@blue.stonehenge.com>
In-Reply-To
<24182.1169759500@lotus.CS.Berkeley.EDU>
>>>>> "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!
Previous: Jason RiedyNext: Simon 'corecode' Schubert
Message 2 of 3 in “Use inttypes.h rather than stdint.h.”
  1. Use inttypes.h rather than stdint.h.Jason Riedy, Jan 25, 2007
  2. Randal L. SchwartzJan 25, 2007
  3. Simon 'corecode' SchubertJan 26, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.