Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cunixf.cc.columbia.edu!sol.ctr.columbia.edu!caen!uwm.edu!ux1.cso.uiuc.edu!news.iastate.edu!IASTATE.EDU!john
From: john@IASTATE.EDU (Hascall John Paul)
Newsgroups: comp.lang.c
Subject: Re: Is typedef char BUFFER[20] legal?
Message-ID: <1991Mar1.103608@IASTATE.EDU>
Date: 1 Mar 91 16:36:08 GMT
References: <1212@tredysvr.Tredydev.Unisys.COM> <1991Jan29.210100.8105@zoo.toronto.edu>
Sender: news@news.iastate.edu (USENET News System)
Reply-To: john@IASTATE.EDU (Hascall John Paul)
Organization: Iowa State University
Lines: 26

In article <1991Jan29.210100.8105@zoo.toronto.edu>, henry@zoo.toronto.edu (Henry
Spencer) writes:
> In article <1212@tredysvr.Tredydev.Unisys.COM>
paul@tredysvr.Tredydev.Unisys.COM (Paul Siu) writes:

> >Can anyone also tell me what is the most common style convention for type
> >names, I usually put them all in capitals.

> Insofar as there is a consensus, it's to put them in lower case with a
> suffix "_t", e.g. "uid_t" as the type for userids.

   Nice; until some standards body steals your name out from under you.
Not to start ``style wars'' again, but another common scheme is:

#define FOO 4
typedef struct {
      char    f_thing;
      int     f_thang[FOO];
} Foo;                        (or FooType, or fooType)
Foo foo;

--
John Hascall                        An ill-chosen word is the fool's messenger.
Project Vincent
Iowa State University Computation Center                       john@iastate.edu
Ames, IA  50011                                                  (515) 294-9551