This is the mail archive of the
mailing list for the Cygwin project.
Re: C COM objects?
- From: Larry Hall <cygwin-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 29 Jan 2004 20:40:06 -0500
- Subject: Re: C COM objects?
- References: <Pine.GSO.4.58.0401291731420.11773@eos>
- Reply-to: Cygwin List <cygwin at cygwin dot com>
At 06:43 PM 1/29/2004, Brian Ford you wrote:
>I admit to know almost nothing about COM objects, but I have been tasked
>to find out if they can be built from code that uses cygwin1.dll services.
>Searching for Cygwin and COM on the web, and in the archives, is difficult
>for the obvious .com reason.
>What I think I do know is that C++ COM objects are probably out because of
>name mangling and vtable issues. I am still unclear about whether the
>libs that implement COM use msvcrt*.dll. I assume if that is true, then
>all COM objects are out because of the newlib conflict.
>Any pointers to C COM object examples or information about using Cygwin
>based code in them would be *greatly* appreciated. If you feel this
>subject is too far OT, then please feel free to ignore my Reply-To header
>and send me personal email. Thanks.
COM doesn't require MSVCRT, though it doesn't preclude it either. So,
depending on what you're doing and what you're using in COM-land, it's
possible to dodge the MSVCRT bullet.
COM is language independent, which means it's possible to use COM
objects from C code. I've never done this though. I remember some
rumblings about people successfully "working with COM" under Cygwin
but it was long ago and I don't remember any details.
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
838 Washington Street (508) 893-9889 - FAX
Holliston, MA 01746
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html