Re: exporting data from a dll - unresolved externals
"2b|!2b==?" <user@domain.invalid> ha scritto nel messaggio
news:9_OdnbzImKJZ5h7anZ2dnUVZ8uadnZ2d@bt.com...
Good idea (although it is a work around), but it means I'll have to
refactor a lot of existing code I have already written. Is there a
TECHNICAL reason why I can't use a class that has been exported ?
Frankly speaking, if I have to build a Win32 DLL, I tend to export a
C-interface. The DLL can be written in C++, of course, but the *interface*
is just plain C.
(Note that also FMOD, an important audio library, does something like this,
at least for FMOD3: C-interface DLL, and I think C++ implementation.)
If I want to export an object model for the DLL, I would use COM (and ATL -
or sometimes MFC - as helper framework/library).
If you don't use COM, you will start implementing custom memory management,
and other things, that COM already has defined and tested and very good
working. (So, no need to reinvent the wheel.)
However, assuming that you are using the same C++ compiler to build the DLL
and to build the DLL client, I think that you can export C++ classes with no
problems, if you do things right.
Giovanni