> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
>> sstream is not present in gcc 2.95.2 (only 2.95.3).
Andre> I know, but it is easily worked around by simply including the
Andre> sstream header file we are using right now.
The other problem (which forces the .str().c_str() stuff) is
> sstream is not present in gcc 2.95.2 (only 2.95.3).
I know, but it is easily worked around by simply including the sstream
header file we are using right now.
Andre'
--
André Pönitz . [EMAIL PROTECTED]
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
>> They are moved in global namespace because if we define our own, we
>> want to define them in global namespace (if only to avoid clashes).
>> Indeed the same should be done for stringstream.
Andre> What are the plans for 1.2.0 anyway?
On Friday 13 July 2001 13:18, Jean-Marc Lasgouttes wrote:
> > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> Is there any reason why istringstream and ostringstream are
> Angus> moved into the global namespace. If so, why isn't stringstream
> Angus> as well. Can I not just re
> They are moved in global namespace because if we define our own, we
> want to define them in global namespace (if only to avoid clashes).
> Indeed the same should be done for stringstream.
What are the plans for 1.2.0 anyway?
Didn't somebody (you(?)) mention g++ 2.95 as minimum requirement lat
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Is there any reason why istringstream and ostringstream are
Angus> moved into the global namespace. If so, why isn't stringstream
Angus> as well. Can I not just remove the using directives and put
Angus> them in the .C files?
They
