Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!csn!ncar!hsdndev!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: Global and Extern Pointers, Arrays
Message-ID: <16244@smoke.brl.mil>
Date: 23 May 91 19:54:06 GMT
References: <AJ3U.91May22202642@agate.cs.virginia.edu>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 15

In article <AJ3U.91May22202642@agate.cs.virginia.edu> aj3u@agate.cs.virginia.edu (Asim Jalis) writes:
>file.1
>	struct x px[1] = { ... };
>file.2
>	extern *px	/* boinks */
>	extern px[]	/* works */
>Any ideas as to why this is?

Sure, but the question is, why would you think it ought to work the
other way, where there is a clear type mismatch?  The only thing I
can think of is that somehow you have gotten the notion that arrays
and pointers are the same thing; that is false, and you should learn
what the difference is and why under SOME circumstances the two types
"seem" to act the same.  I'm sure this information is widely available,
probably in the FAQ list.