typedef names (was: Is typedef char BUFFER[20] legal?)

[David Conrad]

In article <665344102.6268 at mindcraft.com> fred at mindcraft.com (Fred Zlotnick) writes:
>So, if you want your programs to port to POSIX.1 conforming systems, this
>convention is no longer ok.  I had previously used an "_t" suffix for
>typedef names, but have stopped.  My current convention is to use "_T"
>(and to use lower case letters for the rest of the type name), but I'm
>not thrilled with it.  Any suggestions?
>----
>Fred Zlotnick                       |	#include <std.disclaimer>
>fred at mindcraft.com                  |	#include <brilliant.quote>
>...!{decwrl,ames,hpda}!mindcrf!fred |

Yes, I'd like to suggest that the POSIX.1 standard sucks.

Let the programmer have _t, make the system use _t_ or something equally ugly.
--
David Conrad
tygra!dave at uunet.uu.net
tygra!dave at sharkey.cc.umich.edu
(The address in the last line below is BROKEN.)
-- 
=  CAT-TALK Conferencing Network, Computer Conferencing and File Archive  =
-  1-313-343-0800, 300/1200/2400/9600 baud, 8/N/1. New users use 'new'    - 
=  as a login id.  AVAILABLE VIA PC-PURSUIT!!! (City code "MIDET")        =
   E-MAIL Address: dave at DDMI.COM