Re: Why can't you define an external object twice and never use it?

Article View: comp.std.c

Article #896

#896

From: Doug Gwyn
Date: Fri, 10 Nov 1989 19:17

8 lines
768 bytes

In article <53@looney.twinsun.com> eggert@twinsun.com (Paul Eggert) writes:
>	int X = 0;
>	int X = 0;
>However, none of these prohibitions apply to the above program.  What's wrong?

I don't know why you cite constraints on multiple definition;
the real problem is that you have violated the "only one initialization"
constraint.

Technical Details

Message-ID: <11582@smoke.BRL.MIL>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!purdue!haven!adm!smoke!gwyn

References: <53@looney.twinsun.com>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!purdue!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: <11582@smoke.BRL.MIL>
Date: 10 Nov 89 19:17:14 GMT
References: <53@looney.twinsun.com>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 8

Reply to Parent Message