BUG in Boost.Any, from 1.33.1 till HEAD
Hello, I want to propose this bug fix in boost/any.hpp (around line 225): template<typename ValueType> const ValueType * unsafe_any_cast(const any * operand) { //WRONG?!: return any_cast<ValueType>(const_cast<any *>(operand)); return unsafe_any_cast<ValueType>(const_cast<any *>(operand)); } Symptoms are: Boost.Signals does not work properly across shared library boundaries if some compiler options ("-fvisibility=hidden" on GCC) are set. Seeing this bug fixed is very high priority for me. Kind regards, Aristid Breitkreuz
Aristid Breitkreuz <aribrei <at> arcor.de> writes:
Symptoms are: Boost.Signals does not work properly across shared library boundaries if some compiler options ("-fvisibility=hidden" on GCC) are set.
Seeing this bug fixed is very high priority for me.
Fixed in HEAD, revision 1.13. ViewVC page: http://tinyurl.com/nyn8g . -- Alexander Nasonov
Am Montag, den 18.09.2006, 07:46 +0000 schrieb Alexander Nasonov:
Aristid Breitkreuz <aribrei <at> arcor.de> writes:
Symptoms are: Boost.Signals does not work properly across shared library boundaries if some compiler options ("-fvisibility=hidden" on GCC) are set.
Seeing this bug fixed is very high priority for me.
Fixed in HEAD, revision 1.13. ViewVC page: http://tinyurl.com/nyn8g .
Thanks. Will this be merged to 1.34? Aristid Breitkreuz
-- Alexander Nasonov
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Aristid Breitkreuz <aribrei <at> arcor.de> writes:
Fixed in HEAD, revision 1.13. ViewVC page: http://tinyurl.com/nyn8g .
Thanks. Will this be merged to 1.34?
I don't know if I'm allowed to commit to RC_1_34_0. Please, ask Thomas Witt. He is a release manager of 1.34. -- Alexander Nasonov
On 9/21/06, Alexander Nasonov <alnsn@yandex.ru> wrote:
Aristid Breitkreuz <aribrei <at> arcor.de> writes:
Fixed in HEAD, revision 1.13. ViewVC page: http://tinyurl.com/nyn8g .
Thanks. Will this be merged to 1.34?
I don't know if I'm allowed to commit to RC_1_34_0. Please, ask Thomas Witt. He is a release manager of 1.34.
If its a bug, the fix should be merged onto the branch. The branch is supposed to be feature-frozen, not bug-frozen. -- Caleb Epstein
participants (3)
-
Alexander Nasonov -
Aristid Breitkreuz -
Caleb Epstein