This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Latest TR1 draft
>On a related issue, it was mentioned today on the Boost list that they
>will need some mechanism for detecting whether a particular stdlib
>provides TR1 components. This will allow Boost to decide whether to use
>the stdlib's native TR1 components or use Boost's own versions. Could v3
>provide macros such as _GLIBCXX_TR1_MEMORY be used to state which
>headers are available ? Should it be more fine-grained than the header
>name, e.g. _GLIBCXX_TR1_MEMORY_WEAK_PTR ? Or will it be left to the
>Boost developers to solve this problem e.g. by just keeping track in
>their libstdcpp.hpp header of which components are available in
>particular GCC releases ?
I'm in favor of not adding the macros in libstdc++ for each item and
just having boost configure deal with it.
Note that include guards will already be present in any libstdc++
implementation. So, that part will be covered.
If you want to change the guards on array and tuple to be of the consistent, standard form like
_GLIBCXX_TR1_foo
feel free.
-benjamin