Why can't you define an external object twice and never use it?
Doug Gwyn
gwyn at smoke.BRL.MIL
Sat Nov 11 06:17:14 AEST 1989
In article <53 at looney.twinsun.com> eggert at 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.
More information about the Comp.std.c
mailing list