--- Edward Diener <[EMAIL PROTECTED]> wrote: > Exporting/importing C++ classes is completely > implementation dependent, due > mainly to name mangling, and requires a DLL for a > particular > platform/compiler/release to be built.
There are several issues with DLL and C++, to name few: 1. Name mangling 2. Using inline methods in the exported class. 3. Global class instanses in the DLL. How does boost ensure that inline methods don't conflict with the exported methods. The conflict can be platform specific. Is it allowed to have global instances of a class in boost's DLLs? Are there any development policies on how exported C++ classes should be implemented/tested in boost? Eugene __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
