Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site sunybcs.UUCP
Path: utzoo!watmath!clyde!floyd!harpo!seismo!rochester!rocksvax!sunybcs!colonel
From: colonel@sunybcs.UUCP (George Sicherman)
Newsgroups: net.lang.c
Subject: Re: extern declaration inconsistency
Message-ID: <1439@sunybcs.UUCP>
Date: Mon, 9-Apr-84 14:34:04 EST
Article-I.D.: sunybcs.1439
Posted: Mon Apr  9 14:34:04 1984
Date-Received: Thu, 12-Apr-84 05:24:51 EST
References: <1538@mit-eddie.UUCP>
Organization: SUNY/Buffalo Computer Science
Lines: 9

[tail +2]

It's just what you'd expect.  The extern char *c expects to find
a character address stored in a global word.  Instead, it finds
an array of bytes.  If you call it extern char c[] the problem
should go away.

	Col. G. L. Sicherman
...seismo!rochester!rocksvax!sunybcs!colonel