|
Boost : |
From: Jeff Garland (jeff_at_[hidden])
Date: 2002-03-26 12:07:20
> Playing devils advocate, it doesn't always work beautifully. The biggest
> problem occurs when the libraries produced must be usable by other compilers
> or even other languages. The name mangling done by your C++ compiler can
> prevent the DLL from being used by other C++ compilers or by other languages
> that can easily call "C" functions exported from DLLs.
>
> Other than that, though, you can use C++ in DLLs very effectively. In fact,
> many Windows programmers generate and use MFC extension DLLs on a daily
> basis.
On all of these projects we never had the requirement to support multiple C++
compilers. We did however support Perl bindings and for this we had to support
some C interfaces, but these were limited to a relatively small set of
interfaces.
> All that said, none of this really changes the problem domain. There simply
> isn't a universal solution for what the poster wants.
Agreed.
Jeff
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk