Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!elroy.jpl.nasa.gov!ncar!hsdndev!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.std.c
Subject: Re: Pointers to Incomplete Types in Prototypes
Message-ID: <16109@smoke.brl.mil>
Date: 10 May 91 23:58:42 GMT
References: <1991May8.043353.28983@athena.mit.edu> <1991May8.072112.20866@tkou02.enet.dec.com> <1991May10.021509.9862@athena.mit.edu>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 13

In article <1991May10.021509.9862@athena.mit.edu> scs@adam.mit.edu writes:
>That's why I think that the one-line translation unit
>	struct bar *bp;
>is conforming, and need elicit no diagnostic.

Of course it is.  Sheesh, you guys have gotten yourselves confused.

>I admit that there may be some ambiguity here.

X3J11 has already ruled that type information is not "exported" from
an inner scope to an outer one.  It's pretty clear that the type of a
local variable has nothing to do with the type of a global one whose
identifier is temporarily "hidden" by the one in the local scope.