Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!princeton!caip!nike!ucbcad!ucbvax!sdcsvax!sdchem!tps
From: tps@sdchem.UUCP (Tom Stockfisch)
Newsgroups: net.lang.c
Subject: Re: typedef scope mess
Message-ID: <236@sdchema.sdchem.UUCP>
Date: Fri, 13-Jun-86 16:30:40 EDT
Article-I.D.: sdchema.236
Posted: Fri Jun 13 16:30:40 1986
Date-Received: Tue, 17-Jun-86 20:20:39 EDT
References: <1003@g.cs.cmu.edu> <1124@trwrb.UUCP>
Reply-To: tps@sdchema.UUCP (Tom Stockfisch)
Organization: Chemistry Dept, UC San Diego
Lines: 17

>[redefinition of typedef as auto works on one machined but not another...].
>Thus, I would suggest being very careful since
>you never know what compiler your code may see next.  Not only that, but it
>is just plain bad design to overload typedefs, depending on scoping to save
>the functionality of the code.  [Couldn't resist my two cents worth.]
>
>	Dan Jones
>		...!trwrb!jcc-one!djones

Do you also think reusing an *extern* name in a local block is "plain bad
design"?  I can't see the difference.  I agree you should avoid overloading
names, but the idea behind the overloading classes is so you can confidently
define local variables which are guaranteed to be independent of the rest of
your project.  Not having to worry about a typedef defined in some 'include'
file improves modularity.

-- Tom Stockfisch, UCSD Chemistry