Re: [boost] GCC, stringstreams, and boost/config.hpp

From: David Abrahams (abrahams_at_[hidden])
Date: 2001-05-28 21:01:33

How about this?
Targets wishing to use sstream simply #include it.
We add our own <sstream> to the path /behind/ the system #includes, so it
will only be found if the implementation fails to conform. We #define
BOOST_NO_SSTREAM in our <sstream>

-Dave

----- Original Message -----
From: "Jens Maurer" <Jens.Maurer_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Monday, May 28, 2001 3:39 PM
Subject: Re: [boost] GCC, stringstreams, and boost/config.hpp

> David Abrahams wrote:
> >
> > You might also search around to see if the library revision identifies
> > itself separately from the core compiler. One approach might start with
> > taking the diffs between the 2.95.2/3 lib sources and searching for
> > "define".
>
> I've just had a quick look at the diffs between 2.95.2 and 2.95.3.
> The library changed very little, and I couldn't find anything
> to evaluate by the preprocessor to make the distinction.
>
> Jens Maurer
>
>
>
> To unsubscribe, send email to: <mailto:boost-unsubscribe_at_[hidden]>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>