On 17.02.2016, at 17:33, Rene Rivera
wrote: Sorry about the delay.. You should now have an invite for this.
Thanks, seems to work. On the topic of fixing the issue reported: I realize that is_chained_base is actually a PITA when you try to add another namespace around the operator templates. I’ll have to think of a solution. Just a heads up for others: is_chained_base was placed in ::boost, not ::boost::detail. I assume this is an oversight as the documentation does not mention it and a comment in the source is implying that it should actually should have been placed in ::boost::detail. If anyone ever used it as part of the public interface, please speak up now! :)
On Mon, Feb 15, 2016 at 10:58 AM, Daniel Frey
wrote: On 18.01.2016, at 20:47, Andrey Semashev
wrote: On 2016-01-18 22:36, Daniel Frey wrote:
That said, I sympathize with fixing the issue when possible. Maybe we could change the default behavior, but offer the old implementation when the user sets BOOST_PLACE_OPERATORS_IN_NAMESPACE_BOOST. And that is only effective when BOOST_NO_OPERATORS_IN_NAMESPACE is *not* used (to avoid breaking the old compilers). Opinions?
Sounds good to me.
I’d like to actually work on this, but my ticket to get access to Boost.Utility is just sitting idle…
https://github.com/boostorg/admin/issues/111
If the above ticket is not the right way to move forward, please someone let me know what to do instead. Thanks.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost