Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Subject: Re: Is --enable-utf8 working everywhere?
From: Greg Hudson <ghudson@MIT.EDU>
To: Branko =?iso-8859-2?Q?=C8ibej?= <brane@xbc.nu>
Cc: dev@subversion.tigris.org, Apache Apr Mailing List <dev@apr.apache.org>
In-Reply-To: <3D34C4E6.5040909@xbc.nu>
References: <85r8i5c8ee.fsf_-_@newton.ch.collab.net>
			<3D345ADA.B3C49ED5@orcaware.com> <1026856417.3672.120.camel@myware.mynet>
			<3D34A2AC.7F3D417F@orcaware.com> <1026865314.3673.126.camel@myware.mynet>
	<3D34BF26.FF32DF50@orcaware.com>  <3D34C4E6.5040909@xbc.nu>
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: quoted-printable
Date: 17 Jul 2002 12:05:50 -0400
Message-Id: <1026921950.18133.121.camel@error-messages.mit.edu>
Mime-Version: 1.0

On Tue, 2002-07-16 at 21:14, Branko =C8ibej wrote:
> Strictly speaking, Ulrich's patch is better, because there's no=20
> guarantee that "errno" is a simple global variable. It could be=20
> translated into a function call, for all you know -- depends on the=20
> platform, linc implementation, threading support, etc. etc. So making a=20
> copy makes sense.

So it's a function call.  So what?  It still returns a single stable
value.

If you're worried about speed, that's ridiculous.  This is an error
case; a few cycles here or there isn't going to matter.  (And it's not
like errno is ever a slow function call, when it's a function call.)