Path: utzoo!mnetor!tmsoft!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!uunet!olivea!oliveb!amdahl!netcom!avery
From: avery@netcom.COM (Avery Colter)
Newsgroups: comp.lang.c
Subject: Re: Why have xxx_t typedef names (was Re: Is typedef char BUFFER[20] legal?)
Message-ID: <23134@netcom.COM>
Date: 7 Feb 91 19:23:57 GMT
References: <1212@tredysvr.Tredydev.Unisys.COM> <1991Jan29.210100.8105@zoo.toronto.edu> <BEVAN.91Jan30084205@rhino.cs.man.ac.uk> <1991Jan31.172147.21397@zoo.toronto.edu>
Organization: Netcom - Online Communication Services  UNIX System {408 241-9760 guest}
Lines: 18

henry@zoo.toronto.edu (Henry Spencer) writes:

>The purpose is the same as the convention of using uppercase for macro
>names:  to give the poor programmer a little bit more help in figuring
>out what's going on, and to minimize namespace collisions.

It might be, since these seem to be so widespread, that the standards
committee might have sanctioned certain of these xxx_t types as being
standard parameter or return types of some of the standard library
functions.

In the same way that FILE, a typedef'd structure, is the standard
type for a filename under <stdio.h>

-- 
Avery Ray Colter    {apple|claris}!netcom!avery  {decwrl|mips|sgi}!btr!elfcat
(415) 839-4567   "I feel love has got to come on and I want it:
                  Something big and lovely!"         - The B-52s, "Channel Z"