Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!cs.utexas.edu!tut.cis.ohio-state.edu!att!dptg!ulysses!andante!alice!ark
From: ark@alice.UUCP (Andrew Koenig)
Newsgroups: comp.lang.c++
Subject: Re: munch
Keywords: static objects / construction order
Message-ID: <9715@alice.UUCP>
Date: 1 Aug 89 04:32:06 GMT
References: <24096@genrad.UUCP> <9698@alice.UUCP> <218@ssp1.idca.tds.philips.nl>
Organization: AT&T Bell Laboratories, Liberty Corner NJ
Lines: 13

In article <218@ssp1.idca.tds.philips.nl>, roelof@idca.tds.PHILIPS.nl (R. Vuurboom) writes:

> For (1) allow extern declarations (used as forward references) to determine 
> construction order

The trouble with that is that if you're generating C code,
there's no way to pass that information on to the C compiler
that will guarantee that it will find its way correctly to
the linker.  For instance, some C compilers reorder external
declarations to suit themselves.
-- 
				--Andrew Koenig
				  ark@europa.att.com