From: Mark Mitchell <mark@codesourcery.com>
To: Benjamin Kosnik <bkoz@redhat.com>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: RFA: Deprecate C++ options
Date: Sun, 09 Sep 2001 14:22:00 -0000 [thread overview]
Message-ID: <166140000.1000070534@warlock.codesourcery.com> (raw)
In-Reply-To: <200109071713.f87HDFo16914@constant.com>
--On Friday, September 07, 2001 10:13:15 AM -0700 Benjamin Kosnik
<bkoz@redhat.com> wrote:
>
>> Right. I would say my three personal pet peeves, in order, as a C++
>> user, are correctness, compile times, and robustness in the face of
>> errors.
>
> So then.
>
> I'm assuming correctness is being taken care of with the parser rewrite?
Some/much correctness issues, yes. But, lots of front-end things
(builtin operator overloading rules, template instantiation trickiness,
etc.) are not. And, of course, back end bugs are part of correctness
too.
> Compile times can/could be taken care of with a combination of some of
> the inlining work plus pre compiled headers.
Those are partial solutions, but they may be good enough.
> I think it might be wise to establish a target for a release that
> incorporates some of these more far-reaching solutions.
Yes -- but it's too early to do so yet. It's too early to even be
sure we can get the new parser done before October 15th, which is the
cut off for major new features in GCC 3.1.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2001-09-09 14:22 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-07 10:13 Benjamin Kosnik
2001-09-09 14:22 ` Mark Mitchell [this message]
2001-09-12 8:41 ` GCC 3.1 and branches (was: RFA: Deprecate C++ options) Gerald Pfeifer
2001-09-13 16:54 ` Mark Mitchell
2001-09-14 5:35 ` Gerald Pfeifer
2001-09-14 7:16 ` Mark Mitchell
-- strict thread matches above, loose matches on Subject: below --
2001-09-10 1:20 RFA: Deprecate C++ options Bernard Dautrevaux
2001-09-07 10:06 Benjamin Kosnik
2001-09-07 9:41 George Garvey
2001-09-07 10:00 ` Mark Mitchell
2001-09-12 6:27 ` Gerald Pfeifer
2001-09-14 4:02 ` George Gargey
2001-09-14 5:16 ` Gerald Pfeifer
2001-09-06 3:40 Nathan Sidwell
2001-09-06 14:43 ` Mark Mitchell
2001-09-06 15:14 ` Tim Hollebeek
2001-09-06 15:21 ` Joseph S. Myers
2001-09-06 18:23 ` Mark Mitchell
2001-09-06 21:55 ` Zack Weinberg
2001-09-06 22:00 ` Mark Mitchell
2001-09-06 22:11 ` Richard Henderson
2001-09-06 23:50 ` Zack Weinberg
2001-09-06 22:14 ` Richard Henderson
2001-09-06 22:20 ` Mark Mitchell
2001-09-18 4:44 ` Joseph S. Myers
2001-09-18 9:06 ` Mark Mitchell
2001-09-06 23:46 ` Zack Weinberg
2001-09-07 0:03 ` Richard Henderson
2001-09-06 19:16 ` Joe Buck
2001-09-07 8:52 ` George Garvey
2001-09-07 9:03 ` Mark Mitchell
2001-09-07 13:40 ` Jason Merrill
2001-09-10 9:28 ` Nathan Sidwell
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=166140000.1000070534@warlock.codesourcery.com \
--to=mark@codesourcery.com \
--cc=bkoz@redhat.com \
--cc=gcc@gcc.gnu.org \
/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).