From: Mark Mitchell <mark@codesourcery.com>
To: Joe Buck <Joe.Buck@synopsys.com>,
Gabriel Dos Reis <gdr@codesourcery.com>
Cc: Phil Edwards <phil@jaj.com>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
"bkoz@redhat.com" <bkoz@redhat.com>,
"libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>
Subject: Re: rel_ops (was Re: GCC 3.1 Release)
Date: Tue, 16 Apr 2002 10:04:00 -0000 [thread overview]
Message-ID: <92710000.1018976465@gandalf.codesourcery.com> (raw)
In-Reply-To: <200204161647.JAA18056@atrus.synopsys.com>
> I'm not going to ask that the comment be stricken, but I'm not crazy
> about the idea of a lot of editorial commentary in the headers.
I agree. We don't need editorial comments about languages, operating
systems, or other similar things in comments. We really don't even
need editorial comments about GCC itself in comments -- although
saying "if we had this, then we could clean up that" is sometimes a
useful reminder.
But, C++ and its runtime library are what they are; it's up to us to
implement them as well as we can without judging which features we
like and which we don't.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2002-04-16 17:04 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-02 14:38 GCC 3.1 Release Mark Mitchell
2002-04-02 14:47 ` Tom Tromey
2002-04-03 15:06 ` Phil Edwards
2002-04-03 16:08 ` Joe Buck
2002-04-03 17:57 ` Phil Edwards
2002-04-04 10:17 ` Mark Mitchell
2002-04-09 9:48 ` Joe Buck
2002-04-09 10:44 ` Benjamin Kosnik
2002-04-09 11:35 ` Gabriel Dos Reis
2002-04-10 2:37 ` Mark Mitchell
2002-04-10 7:59 ` Joe Buck
2002-04-10 8:17 ` Gabriel Dos Reis
2002-04-10 8:22 ` Joe Buck
2002-04-10 10:14 ` Mark Mitchell
2002-04-10 11:39 ` Benjamin Kosnik
2002-04-10 11:47 ` Paolo Carlini
[not found] ` <flwuvfqrme.fsf@jambon.cmla.ens-cachan.fr>
2002-04-12 5:12 ` Paolo Carlini
2002-04-10 13:01 ` Gabriel Dos Reis
2002-04-11 6:02 ` Joe Buck
2002-04-11 14:58 ` Gabriel Dos Reis
2002-04-10 15:44 ` Fixing libstdc++/3628 (was: Re: GCC 3.1 Release) Paolo Carlini
2002-04-10 15:49 ` Phil Edwards
2002-04-10 17:29 ` Paolo Carlini
2002-04-12 16:10 ` Mark Mitchell
2002-04-12 18:20 ` Paolo Carlini
2002-04-15 17:51 ` GCC 3.1 Release Gabriel Dos Reis
2002-04-15 19:36 ` Gabriel Dos Reis
2002-04-15 19:43 ` Mark Mitchell
2002-04-15 20:03 ` Gabriel Dos Reis
2002-04-16 9:49 ` rel_ops (was Re: GCC 3.1 Release) Joe Buck
2002-04-16 10:04 ` Mark Mitchell [this message]
2002-04-16 10:35 ` Joe Buck
2002-04-16 10:53 ` Gabriel Dos Reis
2002-04-16 11:05 ` Mark Mitchell
2002-04-16 10:49 ` Gabriel Dos Reis
2002-04-17 11:56 ` Richard B. Kreckel
2002-04-17 12:15 ` Joe Buck
2002-04-19 12:54 ` Gabriel Dos Reis
2002-04-17 12:16 ` Phil Edwards
2002-04-17 16:54 ` Joe Buck
2002-04-19 13:19 ` Gabriel Dos Reis
2002-04-19 15:05 ` Joe Buck
2002-04-19 12:59 ` Gabriel Dos Reis
2002-04-19 14:34 ` Phil Edwards
2002-04-19 12:47 ` Gabriel Dos Reis
2002-04-06 7:47 ` GCC 3.1 Release Jason Merrill
2002-04-10 10:17 ` Janis Johnson
2002-04-10 10:24 ` Mark Mitchell
2002-04-10 10:35 ` Christian Jönsson
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=92710000.1018976465@gandalf.codesourcery.com \
--to=mark@codesourcery.com \
--cc=Joe.Buck@synopsys.com \
--cc=bkoz@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdr@codesourcery.com \
--cc=libstdc++@gcc.gnu.org \
--cc=phil@jaj.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).