>> Is it possible to have an ATL project that also contains win32 exported
>> classes and functions?.
[quoted text clipped - 12 lines]
> general issue that Windows has no universal ABI for C++ classes), but if
> you have exported functions you can still do so.
Yes C++ classes can be exported. Albeit not in the since that all
functionality is exposed but it is possible.

Signature
============
Frank Hickman
NobleSoft, Inc.
============
Replace the _nosp@m_ with @ to reply.
Ben Voigt [C++ MVP] - 29 Oct 2007 19:24 GMT
>>> Is it possible to have an ATL project that also contains win32 exported
>>> classes and functions?.
[quoted text clipped - 15 lines]
> Yes C++ classes can be exported. Albeit not in the since that all
> functionality is exposed but it is possible.
These things are safe for sharing C++ code:
Source code.
C-compatible exported functions, with a header with appropriate
declarations, and POD structs.
object v-tables, with either a header with pure interface declarations, IDL,
or a COM type library.
For the latter two you must respect memory ownership and always deallocate
in the same module which performed the allocation.
Anything else is highly compiler-specific, non-portable, and almost certain
to cause trouble with a compiler upgrade.