-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jeffrey Yasskin wrote: > On Mon, Jan 25, 2010 at 10:44 AM, Tres Seaver <tsea...@palladion.com> wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Collin Winter wrote: >> >>> For reference, what are these "obscure platforms" where static >>> initializers cause problems? >> It's been a long while since I had to deal with it, but the "usual >> suspets" back in the day were HP-UX, AIX, and Solaris with non-GCC >> compilers, as well as Windows when different VC RT libraries got into >> the mix. > > So then the question is, will this cause any problems we care about? > Do the problems still exist, or were they eliminated in the time > between "back in the day" and now? In what circumstances do static > initializers have problems? What problems do they have? Can the > obscure platforms work around the problems by configuring with > --without-llvm? If we eliminate static initializers in LLVM, are there > any other problems? > > We really do need precise descriptions of the problems so we can avoid them.
Yup, sorry: I was trying to kick in the little I could remember, but it has been eight years since I wrote / compiled C++ in anger (a decade of work in it before that). MvLs reply sounds *exactly* like the memories I have, though. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkteGGcACgkQ+gerLs4ltQ5SHwCfcQOswX0StFS32U3fFE6RZ5rr z0QAmgKUECEhdZPQhgsNACkRiWrWX0t0 =eXM+ -----END PGP SIGNATURE----- _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
