Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!unisoft!greywolf
From: greywolf@unisoft.UUCP (The Grey Wolf)
Newsgroups: comp.lang.c
Subject: Re: Why have xxx_t typedef names (was Re: Is typedef char BUFFER[20] legal?)
Summary: compile-time evaluation of defined types
Message-ID: <3377@unisoft.UUCP>
Date: 13 Feb 91 23:21: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> <23134@netcom.COM>
Reply-To: greywolf@unisoft.UUCP (The Grey Wolf)
Organization: Foo Bar and Grill
Lines: 33

Is there/will there ever be a compile-time / cpp-time evaluation as to
what types are defined?  For example:

#if typed(stat_t)
.
.
#endif	/* typed(stat_t) */

or even:

#if typed(struct stat)
.
.
#endif	/* typed(struct stat) */

This would eliminate the need for putting that stuff in .h files like
#ifndef _STAT_H_
#define _STAT_H_
.
.
.
#endif	/* !_STAT_H_ */

There are many times I've wanted such a beast.

Also, do typedefs ever make it into an object's/executable's nlist?
'Twould be real nice to be able to determine defined types from the
nlist of the compiled code.
-- 
thought:  I ain't so damb dumn! | Your brand new kernel just dump core on you
war: Invalid argument           | And fsck can't find root inode 2
                                | Don't worry -- be happy...
...!{ucbvax,acad,uunet,amdahl,pyramid}!unisoft!greywolf