From: <llewelly@dbritsch.dsl.xmission.com>
To: Pascal Bleser <pbleser@atos-group.com>
Cc: "Smith, Jack" <jack.smith@csfb.com>, gcc <gcc-help@gcc.gnu.org>
Subject: Re: libstdc++ included?.
Date: Mon, 08 May 2000 06:38:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0005080700190.6355-100000@dbritsch.dsl.xmission.com> (raw)
In-Reply-To: <3916B7DF.A588EB93@atos-group.com>
[snip]
> - libstdc++ - only headers ? Well, the STL consists only of templates
> and
> classes with inline methods (because the methods are always very small
> and inlining definately makes them much faster).
>
Actually, libstdc++, when built, contains static and shared libraries as
well as headers. The library is only mostly templates, and some of these
templates, like std::string, std::ostream, std::fstream, etc are
commonly used, so there is a benefit to putting instantiations of these
templates in a library.
As for getting libstdc++, libstdc++-v2 is packaged with gcc 2.95.2's c++
front end. If you get the gcc-2.95.2.tar.gz tarball, you have
libstdc++-v2 . If you get the gcc-core-2.95.2.tar.gz and
gcc-g++-2.95.2.tar.gz tarballs (you do need both them, despite what I
told another poster a few days ago), you also have libstdc++-v2 .
sourceware.cygnus.com/libstdc++ is the home page for libstdc++-v3.
libstdc++-v3 has many important bugfixes and improvements over
libstdc++-v2, and it may be the standard c++ lib for the next
version of gcc .... but it is still experimental right now.
Note that libg++ is obsolete, and unecessary for almost all c++ programs.
As for Jack Smith, it is unfortunate he had such a bad experience, but
I do not understand how to help him.
[snip]
next prev parent reply other threads:[~2000-05-08 6:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-08 5:23 Smith, Jack
2000-05-08 5:51 ` Pascal Bleser
2000-05-08 6:38 ` llewelly [this message]
2000-05-08 7:28 ` Martin v. Loewis
-- strict thread matches above, loose matches on Subject: below --
2000-05-06 10:47 Ivan Martinez
2000-05-06 13:54 ` llewelly
2000-05-07 10:17 ` Ivan Martinez
2000-05-07 20:07 ` llewelly
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0005080700190.6355-100000@dbritsch.dsl.xmission.com \
--to=llewelly@dbritsch.dsl.xmission.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jack.smith@csfb.com \
--cc=pbleser@atos-group.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).