Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Subject: Re: DirectX8/DirectInput + cygwin
From: Robert Collins <robert.collins@itdomain.com.au>
To: cygwin@cygwin.com
In-Reply-To: <20020206203254.GD14490@redhat.com>
References: <002301c1aef8$228e5440$2801a8c0@dcuthbert2k>
	<3C610F7E.5020306@syntrex.com> <20020206172903.GE31367@redhat.com>
	<3C6171A9.2080702@syntrex.com> <20020206181851.GF11730@redhat.com>
	<035a01c1af4b$b598e9f0$a7eb0544@CX535256D> 
	<20020206203254.GD14490@redhat.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: 07 Feb 2002 14:11:43 +1100
Message-Id: <1013051503.1810.2.camel@robertlinux>
Mime-Version: 1.0

On Thu, 2002-02-07 at 07:32, Christopher Faylor wrote:
> On Wed, Feb 06, 2002 at 12:20:23PM -0800, Barubary wrote:
> >What about the more important problem that Microsoft's patented virtual
> >table system, which COM uses, isn't supported by GCC?
> 
> Aren't virtual tables a feature of "C++"?

Yes and no. [D]COM[++], which is not C++, also uses virtual tables for
in-process objects and in-process object stubs. (stubs are used where
the obejct doesn't directly implement an in-process capability, or it's
being invoked remotely). 

However, AFAIK (not an expert) that shouldn't be an issue for us, as all
COM linking is done at run-time, not statically...

Rob


--
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/