From: Tom Tromey <tromey@redhat.com>
To: archer@sourceware.org
Cc: Yao Qi <qiyaoltc@gmail.com>
Subject: Re: C++ draft
Date: Wed, 29 Jun 2011 20:08:00 -0000 [thread overview]
Message-ID: <m3y60kwgcy.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20110628122135.GB3005@redhat.com> (Gary Benson's message of "Tue, 28 Jun 2011 13:21:35 +0100")
Gary> As I understand it, I don't know that there's any reason C++ has to
Gary> use more memory than C. Granted there are things like the STL that
Gary> generate vastly more code under the hood than you might expect, but
Gary> I don't think anybody is talking about using STL here.
Actually, I think we do want to use the STL. At the very least it would
put us on track to get rid of vec.h, our home-grown std::vector. But we
also use or want to use other containers.
Tom
next prev parent reply other threads:[~2011-06-29 20:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 21:08 Tom Tromey
2011-06-27 21:23 ` [Archer] " Joel Brobecker
2011-06-29 19:55 ` Tom Tromey
2011-06-29 21:47 ` [Archer] " Joel Brobecker
2011-06-28 4:33 ` Matt Rice
2011-06-28 8:21 ` Yao Qi
2011-06-28 12:21 ` Gary Benson
2011-06-28 17:08 ` Matt Rice
2011-06-28 17:36 ` Jan Kratochvil
2011-06-29 20:08 ` Tom Tromey [this message]
2011-06-29 20:06 ` Tom Tromey
2011-06-30 6:06 ` Yao Qi
2011-09-26 21:01 ` Jim Blandy
2011-06-29 18:52 ` Stan Shebs
2011-06-29 19:03 ` [Archer] " Joel Brobecker
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=m3y60kwgcy.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=archer@sourceware.org \
--cc=qiyaoltc@gmail.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).