dxb@genrad.com (Daniel A. Burkhard) (07/28/89)
I need some way to control the order of construction of static objects. We are running Glockenspiel's Designer C++ 1.2.E on Suns. Their version of munch (mxx) operates on executables. I realize that this issue has been discussed here earlier -- and if I'm correct, somebody posted a solution. Unfortunately I missed it -- my apologies! Dan Burkhard GenRad Inc. 300 Baker Ave. e-mail : dxb@genrad.com Concord, MA 01742 Tf : (508) 369-4400
ark@alice.UUCP (Andrew Koenig) (07/29/89)
In article <24096@genrad.UUCP>, dxb@genrad.com (Daniel A. Burkhard) writes: > I need some way to control the order of construction > of static objects. I and others have thought for some time about doing it and have yet to come up with a way of specifying the order that is (a) useful, (b) consistent, and (c) not too hard to implement. Let me know if you find one. -- --Andrew Koenig ark@europa.att.com
roelof@idca.tds.PHILIPS.nl (R. Vuurboom) (07/31/89)
In article <9698@alice.UUCP> ark@alice.UUCP (Andrew Koenig) writes: >In article <24096@genrad.UUCP>, dxb@genrad.com (Daniel A. Burkhard) writes: > >> I need some way to control the order of construction >> of static objects. > >I and others have thought for some time about doing it >and have yet to come up with a way of specifying the >order that is (a) useful, (b) consistent, and (c) not >too hard to implement. Let me know if you find one. >-- I know I've got to be missing something here but am curious to find out. A (at least to me) "obvious" solution comes to mind so I'm wondering which of the above (a,b,c) it must be breaking (or whether I understand the problem properly). Assumedly, you'ld want control over (1) construction order of static objects in the same file and control over (2) construction order of (groups of) statics in different files. For (1) allow extern declarations (used as forward references) to determine construction order: extern int you; extern int me; static int me; f() { static int you; } would specify that you is to be constructed before me. For (2) order of linkage determines order of construction of the various groups of statics. Consistency problems are obvious with (2) so how far would specifying (1) alone get you if unacceptable? Note,by the way, that by asking the user to include as first header your header with forward references you could always override the ordering given by (2) (I think :-). And (naturally) you've noted that the above technique(s) won't break existing code (I hope) nor change existing semantics. -- I don't know what the question means, but the answer is yes... (overheard on comp.lang.misc) Roelof Vuurboom SSP/V3 Philips TDS Apeldoorn, The Netherlands +31 55 432226 domain: roelof@idca.tds.philips.nl uucp: ...!mcvax!philapd!roelof
sharp@cadnetix.COM (Jim Sharpe) (08/01/89)
In article <24096@genrad.UUCP> dxb@genrad.com (Daniel A. Burkhard) writes: >I need some way to control the order of construction >of static objects. >We are running Glockenspiel's Designer C++ 1.2.E on Suns. >Their version of munch (mxx) operates on executables. > I don't know if it is good, bad or ugly but the only way that I personaly have seen user controlled static constructor ordering comes with the ET++ package from the University of Zurich. I believe it is just a minor patch to the CC script (1.2.1 from ATT). No guarantees, just another place to look. Jim Sharpe (303) 444-8075 x 686 Cadnetix Corporation Internet: sharp@cadnetix.com 5775 Flatiron Pkwy. UUCP: cadnetix!sharp Boulder, CO 80301 {uunet,boulder,nbires}!cadnetix!sharp
grunwald@flute.cs.uiuc.edu (Dirk Grunwald) (08/01/89)
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: extern int you; extern int me; -- unless you mung the symbols into some other name, munch, which reads `nm' output won't see them in the same order. You could do something like: void *StaticConstructorOrder = { (void *) &you, (void *) &me }; and have munch look for StaticConstructorOrder. -- Dirk Grunwald -- Univ. of Illinois (grunwald@flute.cs.uiuc.edu)
ark@alice.UUCP (Andrew Koenig) (08/01/89)
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