Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch
Newsgroups: comp.lang.c
Subject: Re: Portable way of reading str[4] as uint32_t
Date: Sat, 04 Apr 2020 19:28:55 -0700
Organization: A noiseless patient Spider
Lines: 18
Message-ID: <867dyuoec8.fsf@linuxsc.com>
References: <40d1f926-8737-4332-93f2-c37c46f731f9@googlegroups.com> <5a25b5b4-bd49-4a4a-a64b-3799a000b7f9@googlegroups.com> <86eet5pbgc.fsf@linuxsc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: reader02.eternal-september.org; posting-host="33313a58d422a0b61b629db649debaea"; logging-data="19606"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/G/fndJPslqnAachxtdHVriseNdPiQzSg="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:0yW5MRlJV574BhO4bTc40H10z9A= sha1:TqhY1QykxS7+NOYsqfs+zXSLn9c=
Xref: csiph.com comp.lang.c:151040
Spiros Bousbouras writes:
> On Thu, 02 Apr 2020 19:09:07 -0700
> Tim Rentsch wrote:
>
>> Spiros Bousbouras writes:
>>
>>> I note also that to have uint32_t you need
>>> #include
>>
>> Actually not, because was already #include'd.
>> See for example the man page for htonl().
>
> is not part of standard C.
That statement notwithstanding, it is still true that the
type uint32_t may be used after a (successful) #include
of , without having to #include