Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: A Simple Real World Benchmark for cygwin
From: Robert Collins <rbcollins@cygwin.com>
To: cygwin@cygwin.com
In-Reply-To: <20020903135135.Z12899@cygbert.vinschen.de>
References: <20020902155542.GC14051@redhat.com>
	<CHEDKHJJDLOCCOFLMGEAOEHMCLAA.dvasaru@broadpark.no>
	<20020902220234.GA22844@redhat.com>
	<20020903102756.V12899@cygbert.vinschen.de>
	<1031045914.3d74831ad243d@mail.broadpark.no> 
	<20020903135135.Z12899@cygbert.vinschen.de>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature";
	boundary="=-Zqu5pipC4FHNm9dbD90Q"
Date: 03 Sep 2002 21:59:57 +1000
Message-Id: <1031054399.31077.52.camel@lifelesswks>
Mime-Version: 1.0

--=-Zqu5pipC4FHNm9dbD90Q
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2002-09-03 at 21:51, Corinna Vinschen wrote:

> Yep, that's the problem.  And the reasoning for calling CoInit/CoUnint
> always as pair here since there's no way to rely on that the application
> will *not* call CoUnit somewhere in the middle of its processing.

If it does, and it didnt' call CoInit, it is an application bug, and not
our problem. Thats why there is the requirement to pair the calls - to
allow us to call it once when we need it, and once on shutdown. If we
need to call it once per thread, then IMO we simply set a per-thread
flag when we have called it.
=20
Rob


--=-Zqu5pipC4FHNm9dbD90Q
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQA9dKQ9I5+kQ8LJcoIRAr02AJ0UdNsQXHbYqfyKxd560aiBPK4TCACfUTIR
2/8j2fZyQov+UivuE73hL88=
=+x5O
-----END PGP SIGNATURE-----

--=-Zqu5pipC4FHNm9dbD90Q--