Tom wrote in message <39c7b5dc.101391873@reading.news.pipex.net>...

>>In the g++ implementation, I see no trace of this stuff. Similarly, stringstreams have different names in that
library, i.e. not the ones described by Stroustrup. For instance, there is no header file with the name "sstream".
>
>All true, although the next stable gcc release should fix this by
>including libstdc++3 with gcc.

You can also get a complete implementation of the Standard C++ library today,
for use with gcc under PC/Linux or Sparc/Solaris, from Dinkumware. But it ain't
free.

P.J. Plauger
Dinkumware, Ltd.
http://www.dinkumware.com



---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html              ]

Hello,

I have a little question regarding g++ and the C++ standard. In his book (3rd edition), Stroustrup discusses a template class std::basic_ostream, of which ostream is an instance:

typedef basic_ostream<char> ostream;

In the g++ implementation, I see no trace of this stuff. Similarly, stringstreams have different names in that library, i.e. not the ones described by Stroustrup. For instance, there is no header file with the name "sstream".

Does anyone care to comment on why this is so? Isn't the Standard Library part of the ANSI/ISO standard for C++?

Thanks!

David.

---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html              ]

<bragason@haan.brain.uni-freiburg.de> wrote in message
news:8q643e$m48$2@n.ruf.uni-freiburg.de...
> Hello,
>
> I have a little question regarding g++ and the C++ standard. In his book
(3rd edition), Stroustrup discusses a template class std::basic_ostream, of
which ostream is an instance:
>
> typedef basic_ostream<char> ostream;
>
> In the g++ implementation, I see no trace of this stuff. Similarly,
stringstreams have different names in that library, i.e. not the ones
described by Stroustrup. For instance, there is no header file with the name
"sstream".
>
> Does anyone care to comment on why this is so? Isn't the Standard Library
part of the ANSI/ISO
> standard for C++?

Yes, but release versions of G++ are way behind in this regard. See
www.stlport.org for an excellent solution.

-Dave

---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html              ]

[cc'd to poster]


 <bragason@haan.brain.uni-freiburg.de> wrote:
+ Does anyone care to comment on why this is so? Isn't the Standard Library
+ part of the ANSI/ISO standard for C++?

Yes, and yes.

There are two existing versions of the g++ library for Standard C++.
They are called libstdc++-v2 and -v3.  (Forget "libg++".)

v2 was written before the ISO Committee finished the Standard.  v2 is
horribly outdated and very nonstandard.  It's going to stay that way.

v3 is a complete rewrite.  All the C++ people have stopped working on v2 and
have been working on v3.  When finished, it will be fully ISO-C++-compliant,
with a few bells and whistles thrown in.

The last release of GCC (g++) shipped with v2.  Since then, v3 has been
merged into the GCC master source tree.  Current snapshots include both
v2 and v3; you chose between them when building the compiler.

The v3 homepage is

   http://sources.redhat.com/libstdc++/

Don't be fooled by the URL; Redhat isn't in charge of the project; they're
just donating the machine to host it all.  It'll work anywhere g++ works.


Luck++;
Phil

--
pedwards at disaster dot jaj dot com  |  pme at sources dot redhat dot com
devphil at several other less interesting addresses in various dot domains
The gods do not protect fools.  Fools are protected by more capable fools.

---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html              ]

On Tue, 19 Sep 2000 18:49:34 GMT, bragason@haan.brain.uni-freiburg.de
() wrote:

>Hello,
>
>I have a little question regarding g++ and the C++ standard. In his book (3rd edition), Stroustrup discusses a template class std::basic_ostream, of which ostream is an instance:
>
>typedef basic_ostream<char> ostream;
>
>In the g++ implementation, I see no trace of this stuff. Similarly, stringstreams have different names in that library, i.e. not the ones described by Stroustrup. For instance, there is no header file with the name "sstream".

All true, although the next stable gcc release should fix this by
including libstdc++3 with gcc.

>
>Does anyone care to comment on why this is so?

They are in the process up updating the library, but haven't quite
finished yet. If you get the latest snapshot of gcc you will find that
this has been fixed. Alternatively, STLport from www.stlport.org works
very well with gcc and is the solution I have gone for.

> Isn't the Standard Library part of the ANSI/ISO standard for C++?

Oh yes.

Tom

---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html              ]