On 1/7/07, Robert Ramey
Robert wrote:
skip "export" and just use "register" to register your derived types.
I've done that now for LogMessage only (as a special case), registering only if I know its a LogMessage from its 'type' member. Other derived classes are exported using the macro. Thanks for the help.
sadrok wrote:
I believe I have found the source of my problem. My program is basically dynamically loading another module and forking a process to run that module in. Both the parent module and the client module had the LogMessage class exported by boost. Since the client inherited the memory space of the parent this caused the troubles. Now I will just figure out an elegant way to make sure that the LogMessage gets exported only once.
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
-- sadrok@gmail.com Yahoo! IM: sadrok_za Jabber ID: sadrok@jabber.obsidian.co.za