Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: Naming convention for structs and types Date: Thu, 12 Jan 2017 13:26:42 -0800 Organization: None to speak of Lines: 27 Message-ID: References: <316df0b2-5692-4eff-8ec7-41ad9ff08d17@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="768745921b79448f5a531b86aeb60d71"; logging-data="31379"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/+YFAW7GvQN11Q+8ohNuMu" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:EtSB0WiO+WiZesaf79pXCDTTfmk= sha1:keYcHweMu+QBXyu0nULU0Yo+VPY= Xref: csiph.com comp.lang.c:101557 Richard Heathfield writes: > On 12/01/17 20:50, Keith Thompson wrote: >> Richard Heathfield writes: >>> On 12/01/17 20:01, luser droog wrote: >>> >>>> >>>> The trailing _t is actually reserved for the implementation, >>> >>> Certainly true for int*_t and uint*_t, but do you have a citation for >>> the more general claim? >> >> I think it's a POSIX rule. > > So do I, but I can't find any reference to it in the POSIX Standard. http://pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html Search for the phrase "ANY header" at the bottom of the table in section 2.2.2. [...] -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"