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 12:50:52 -0800 Organization: None to speak of Lines: 16 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="U2FsdGVkX18/U4IaTx6iXvi0JtXqcygt" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:4scLqj7nDDlSzqz0teOqz5za4JY= sha1:ShpTOTcJnN7HGpkqaH4uJiFSiv0= Xref: csiph.com comp.lang.c:101551 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. -- 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"