Mailing-List:	contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT cygwin DOT com>
List-Help:	<mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin-developers AT cygwin DOT com
Date:	Thu, 8 Aug 2002 11:33:38 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin-developers AT cygwin DOT com
Subject:	Re: FYI on private static object construction
Message-ID:	<20020808153338.GD8388@redhat.com>
Reply-To:	cygwin-developers AT cygwin DOT com
Mail-Followup-To:	cygwin-developers AT cygwin DOT com
References:	<3D527A3C DOT 40704 AT hekimian DOT com> <20020808152748 DOT GA8388 AT redhat DOT com>
Mime-Version:	1.0
In-Reply-To:	<20020808152748.GA8388@redhat.com>
User-Agent:	Mutt/1.3.23.1i

On Thu, Aug 08, 2002 at 11:27:48AM -0400, Christopher Faylor wrote:
>On Thu, Aug 08, 2002 at 10:03:40AM -0400, Joe Buehler wrote:
>>It appears from discussion on the gcc list that private static
>>objects in C++ functions are constructed when they are encountered
>>in program flow.  E.g.:
>>
>>So I would recommend that in Cygwin such objects be moved out of
>>functions to global scope, to avoid threading issues.
>
>What functions are you talking about?  Private static functions are
>unsafe in a threaded application by default.

Sorry.  Make that "private static variables".

cgf

- Raw text -