Re: [Boost-users] Problem with boost::any?

Subject: Re: [Boost-users] Problem with boost::any?
From: Emil Dotchevski (emildotchevski_at_[hidden])
Date: 2009-01-12 18:09:59

On Mon, Jan 12, 2009 at 12:59 PM, Germán Diago <germandiago_at_[hidden]> wrote:
>
> Very helpful. Solved the problem. I'm using boost version 1.35. Was this
> corrected in boost 1.37?
> Thanks in advance.
>
>> https://svn.boost.org/trac/boost/ticket/754

Isn't this a problem of using the incorrect visibility options and/or
dlopen flags? My plugin system (including its use of std::type_info,
and including dynamic unloading) works fine on Windows and LINUX, so
unless you're hitting some kind of version-specific bug, you might be
doing something wrong.

I am strongly against using string comparisons for std::type_info
objects because A) they might not work, B) if this was the right thing
to do the compiler would be doing it that way (as MSVC does), and C)
it would do nothing to solve the more general problem, which has to do
with symbol visibility. If your std::type_info comparison is broken,
then comparing function pointers and other compiler-generated objects
is broken too.

Emil Dotchevski
Reverge Studios, Inc.
http://www.revergestudios.com/reblog/index.php?n=ReCode