Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #161449
| From | James Kuyper <jameskuyper@alumni.caltech.edu> |
|---|---|
| Newsgroups | comp.lang.c |
| Subject | Re: comp.std.c |
| Date | 2021-06-16 20:48 -0400 |
| Organization | A noiseless patient Spider |
| Message-ID | <sae65c$c9q$1@dont-email.me> (permalink) |
| References | <20210613161342.0000272f@hotmail.com> <87k0mty400.fsf@nosuchdomain.example.com> <eli$2106161626@qaz.wtf> <87pmwlk02d.fsf@bsb.me.uk> <eli$2106161651@qaz.wtf> |
On 6/16/21 7:51 PM, Eli the Bearded wrote: > In comp.lang.c, Ben Bacarisse <ben.usenet@bsb.me.uk> wrote: ... >> Historically, this group has discussed many topics related to C. Some >> of the best threads have been prompted by "how would you write this?" >> questions. > > I probably exaggerate a bit, but say the "#include <stdint.h>" thread > gets into standard related questions and answers: > > > Keith Thompson in <87wnqxxoe3.fsf@nosuchdomain.example.com>: > SIMON [ in <sa5vrs$7d3$1@dont-email.me> ]: > > I was in the opinion that stdint.h is cross-compiler/cross- > > platform compliant. > > It is -- but none of the exact-width types are guaranteed to exist > (though the 8, 16, 32, and 64 bit ones almost certainly will on > typical systems). > > <inttypes.h> provides macros that expand to appropriate format strings. > <inttypes.h> includes <stdint.h>, so you don't need to include both, > though you can. Discussions about what the standard actually says are on-topic in both groups. Discussions about changes to what it says go on comp.std.c, while questions about the best way to right your code, based upon what it says in the standard, go on comp.lang.c.
Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Why the fuck is this newsgroup banned AGAIN on google newsgroups ?! Skybuck Flying <skybuck2000@hotmail.com> - 2021-06-13 16:13 +0200
Re: Why the fuck is this newsgroup banned AGAIN on google newsgroups ?! (news.eternal-september.org) olcott <NoOne@NoWhere.com> - 2021-06-13 09:17 -0500
Re: Why the fuck is this newsgroup banned AGAIN on google newsgroups ?! DFS <nospam@dfs.com> - 2021-06-16 13:30 -0400
Re: Why the fuck is this newsgroup banned AGAIN on google sandy sharma <sandysandy7899@gmail.com> - 2021-06-16 18:00 +0000
Re: Why the fuck is this newsgroup banned AGAIN on google Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2021-06-16 12:59 -0700
comp.std.c (was: Re: Why the fuck is this newsgroup banned AGAIN on google) Eli the Bearded <*@eli.users.panix.com> - 2021-06-16 20:27 +0000
Re: comp.std.c Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-06-16 21:48 +0100
Re: comp.std.c Eli the Bearded <*@eli.users.panix.com> - 2021-06-16 23:51 +0000
Re: comp.std.c Real Troll <real.troll@trolls.com> - 2021-06-17 00:10 +0000
Re: comp.std.c James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-06-16 20:48 -0400
Re: comp.std.c Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-06-17 02:00 +0100
Re: comp.std.c James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-06-16 23:15 -0400
Re: comp.std.c David Brown <david.brown@hesbynett.no> - 2021-06-17 09:38 +0200
Re: comp.std.c (was: Re: Why the fuck is this newsgroup banned AGAIN on google) Kaz Kylheku <563-365-8930@kylheku.com> - 2021-06-16 21:22 +0000
use Free news.eternal-september.org and Free Thunderbird instead of Google groups olcott <NoOne@NoWhere.com> - 2021-06-16 17:59 -0500
Re: comp.std.c Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2021-06-16 16:23 -0700
Re: comp.std.c Sjouke Burry <burrynulnulfour@ppllaanneett.nnll> - 2021-06-17 02:12 +0200
Re: comp.std.c (was: Re: Why the fuck is this newsgroup banned AGAIN on google) James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-06-16 20:43 -0400
Re: Why the fuck is this newsgroup banned AGAIN on google newsgroups ?! Jan van den Broek <balglaas@dds.nl> - 2021-06-17 14:12 +0000
csiph-web