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
From:	"Paul G." <pgarceau AT attbi DOT com>
Organization:	Paul G.
To:	Robert Collins <rbcollins AT cygwin DOT com>
Date:	Wed, 2 Oct 2002 17:06:03 -0700
MIME-Version:	1.0
Subject:	Re: .dll question
Reply-to:	pgarceau AT attbi DOT com
CC:	cygwin AT cygwin DOT com
Message-ID:	<3D9B277B.23243.6D8AC8@localhost>

Thank you, Rob.

On 3 Oct 2002 at 9:19, Robert Collins wrote:

> On Thu, 2002-10-03 at 09:13, Paul G. wrote:
> 
> > 	On a related note, can Cygwin generate c++ .dlls which are loadable by msvc++ or 
> > 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

		Paul G.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -