Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Subject: Re: .dll question
From: Robert Collins <rbcollins AT cygwin DOT com>
To: pgarceau AT attbi DOT com
Cc: cygwin AT cygwin DOT com
In-Reply-To: <3D9B1B11.16005.3D0BDC@localhost>
References: <3D9B1B11 DOT 16005 DOT 3D0BDC AT localhost>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature";
	boundary="=-fXLaRtR4sQZNVZ8j2VTo"
Date: 03 Oct 2002 09:19:35 +1000
Message-Id: <1033600781.14524.221.camel@lifelesswks>
Mime-Version: 1.0

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

On Thu, 2002-10-03 at 09:13, Paul G. wrote:

> 	On a related note, can Cygwin generate c++ .dlls which are loadable by m=
svc++ or=20
> does Microsofts'  method of name mangling prohibit such things?

No it can't. In general, C++ compilers don't interoperate. The C++-Lite
FAQ has a section on this.

From memory, the issues are:
*name mangling
*VMT layout
*new[] management
*exception handling

If you want to use cygwin C++ from MSVC, write some C bindings for the
code.

Rob
--=20
---
GPG key available at: http://users.bigpond.net.au/robertc/keys.txt.
---

--=-fXLaRtR4sQZNVZ8j2VTo
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)

iD8DBQA9m38HI5+kQ8LJcoIRAsFrAKDDn0Wkdo7wPsXiZsoExxGAAu3QkwCgtFLj
KE5TFYYJYPrWKnJf4KyZ4hQ=
=MRNA
-----END PGP SIGNATURE-----

--=-fXLaRtR4sQZNVZ8j2VTo--