From owner-freebsd-current@FreeBSD.ORG  Sun Aug 15 17:02:28 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id DCB2316A4D6; Sun, 15 Aug 2004 17:02:28 +0000 (GMT)
Received: from tensor.xs4all.nl (tensor.xs4all.nl [194.109.160.97])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 82A6F43D48; Sun, 15 Aug 2004 17:02:28 +0000 (GMT)
	(envelope-from dimitry@andric.com)
Received: from kilgore.dim (kilgore.dim [192.168.0.3])
	(using TLSv1 with cipher AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tensor.xs4all.nl (Postfix) with ESMTP id EEB9922852;
	Sun, 15 Aug 2004 19:02:25 +0200 (CEST)
Date: Sun, 15 Aug 2004 19:02:02 +0200
From: Dimitry Andric <dimitry@andric.com>
X-Mailer: The Bat! (v2.12.03) Business
X-Priority: 3 (Normal)
Message-ID: <1526906437.20040815190202@andric.com>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
In-Reply-To: <932D0AB64B5988A5BC8FFBAF@aslan.scsiguy.com>
References: <Pine.GSO.4.43.0408151001050.15254-100000@sea.ntplx.net>
 <200408151553.32463.dfr@nlsystems.com>
 <932D0AB64B5988A5BC8FFBAF@aslan.scsiguy.com>
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature";
	micalg="pgp-sha1";  boundary="----------533D1FF33D213B4"
cc: Daniel Eischen <deischen@freebsd.org>
cc: Johan Pettersson <manlix@demonized.net>
cc: Stefan Ehmann <shoesoft@gmx.net>
cc: freebsd-current@freebsd.org
Subject: Re: New nvidia drivers available
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Aug 2004 17:02:29 -0000

------------533D1FF33D213B4
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

On 2004-08-15 at 17:00:56 Justin T. Gibbs wrote:

> I thought that static constructor invocation was deterministic based
> on link order.  Does the C++ spec really indicate that the order of
> construction can be random?

The spec only says "implementation-defined" and "not guaranteed" (see
section 3.6.2, point 3 of the ISO C++ spec), so you're on your own, it
seems. :)  See also:

http://www.parashift.com/c++-faq-lite/ctors.html#faq-10.11
([10.11] What's the "static initialization order fiasco"?)

Of course, in most cases, any static constructors will be called in
the order that you link them in.  But there's no guarantee
whatsoever...

------------533D1FF33D213B4
Content-Type: application/pgp-signature

-----BEGIN PGP MESSAGE-----
Version: GnuPG v1.2.4 (MingW32)

iD8DBQFBH5cKsF6jCi4glqMRAn15AJ43w9T7vj+CiDgvseTMGShUFob7zACfamMr
ZNqfxEEymZ4txZu7OUk40TU=
=uDCa
-----END PGP MESSAGE-----

------------533D1FF33D213B4--