Boost :

Date view	Thread view	Subject view	Author view

Subject: Re: [boost] [Boost-build] Turn on _GLIBCXX_DEBUG with <runtime-debugging>on
From: Mathias Gaunard (mathias.gaunard_at_[hidden])
Date: 2012-10-25 17:25:20

Next message: Jeffrey Lee Hellrung, Jr.: "Re: [boost] tuple benchmarks show marked differences from std::tuple(was Re: Interesting article on stack-based TMP"
Previous message: Larry Evans: "Re: [boost] tuple benchmarks show marked differences from std::tuple(was Re: Interesting article on stack-based TMP"
In reply to: Matthew Chambers: "[boost] [Boost-build] Turn on _GLIBCXX_DEBUG with <runtime-debugging>on (was: Trivial issues have been neglected.)"
Next in thread: Dave Abrahams: "Re: [boost] [Boost-build] Turn on _GLIBCXX_DEBUG with <runtime-debugging>on"
Reply: Dave Abrahams: "Re: [boost] [Boost-build] Turn on _GLIBCXX_DEBUG with <runtime-debugging>on"

On 25/10/12 16:56, Matthew Chambers wrote:
> I'm forwarding this from the boost-build list to get a broader
> perspective from boost users and probably also some Boost.Build users
> that don't monitor that list.
>
> How many agree with Steven that for <variant>debug:
> "The libraries that are built need to be ABI compatible with code that
> isn't compiled using Boost.Build."
>
> How many would sacrifice ABI compatibility in order for
> <runtime-debugging>on to actually do something for GCC?

Don't sacrifice ABI compatibility.
Make a superdebug variant or something.

Date view	Thread view	Subject view	Author view

Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk