Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<004701c0d474$376f26a0$0200a8c0@lifelesswks>
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	"Dmitry Timoshkov" <dmitry AT sloboda DOT ru>
Cc:	<cygwin AT cygwin DOT com>
References:	<002901c0d47c$255059f0$78752ec3 AT dima>
Subject:	Re: oldhand cygwinner needed: RE: __errno_location() like functionality in Cygwin
Date:	Fri, 4 May 2001 18:28:35 +1000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime:	04 May 2001 08:23:21.0278 (UTC) FILETIME=[7ACA4DE0:01C0D473]

----- Original Message -----
From: "Dmitry Timoshkov" <dmitry AT sloboda DOT ru>
To: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
Cc: <cygwin AT cygwin DOT com>
Sent: Friday, May 04, 2001 7:23 PM
Subject: Re: oldhand cygwinner needed: RE: __errno_location() like
functionality in Cygwin


> First of all, thank you very much for your reply.
>
> "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au> wrote:
>
> [...]
>
> I'm not writing a threaded application, I'm going to port an existing
one,
> which contains a lot of lines of code. Moreover, interoperability with
the
> existing application is one of the requirements: i.e. bug fixes and
improvements
> from the one side should be easy applied to another one. That
application
> uses only those libc calls which are supposedly thread safe, and has
no
> any problems running in Linux. Having thread local errno variable is
enough.

Fair enough.

> > > The second method requires to assign _impure_ptr to the
> > > pointer of thread local reent
> > > structrure before EVERY libc call. Am I understand it correctly?
> >
> > Uhmm, I have no idea what you mean here. You should have _no_ static
> > variables that are unguarded (ie don't use mutexs) and all global
> > structs should have their access guarded.
>
> From the info regarding reentrancy in libc:

Which libc? And the internal programmers guide or the users guide?

Rob


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -