Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!brutus.cs.uiuc.edu!uakari.primate.wisc.edu!aplcen!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.std.c
Subject: Re: Why can't you define an external object twice and never use it?
Message-ID: <11593@smoke.BRL.MIL>
Date: 14 Nov 89 14:31:20 GMT
References: <53@looney.twinsun.com> <11582@smoke.BRL.MIL> <54@looney.twinsun.com>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 11

In article <54@looney.twinsun.com> eggert@twinsun.com (Paul Eggert) writes:
->the real problem is that you have violated the "only one
->initialization" constraint.
-Where is this constraint written down?  It's not in either pANS 3.5.7
-("Initialization") or pANS 3.7 ("External definitions"), where I would
-have expected it.  I fear it was so obvious that it wasn't written
-down anywhere.

It's there somewhere; I remember seeing it a few days ago while
looking for something else.  Maybe it's part of the definition
of an object.