http://gcc.gnu.org/bugzilla/show_bug.cgi?id=1773
--- Comment #86 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot
Uni-Bielefeld.DE> 2011-07-21 12:44:59 UTC ---
> --- Comment #85 from Paolo Carlini <paolo.carlini at oracle dot com>
> 2011-07-21 12:34:21 UTC ---
> Fair enough, and I should really find the time to go again through the entire
> trail. Just wanted to add that for a C header to be 'C++ ready' is a rather
> vaguely defined notion, thus, whereas I can definitely trust my new colleagues
> that something consistent and sane is in place in the Solaris headers, I still
> fear too much special casing in v3. Well, we could also imagine properly
> defining the macros *only* on linux and Solaris at some point, and gradually
> ask the port maintainers to work out the missing bits on their ports.
You should find a description of the problems I found in this thread:
Allow __cplusplus=199711L to work with Solaris 2 headers
http://gcc.gnu.org/ml/libstdc++/2011-03/msg00032.html
Thanks.
Rainer
