From: Mark Mitchell <mark@codesourcery.com>
To: Nicola Pero <nicola@brainstorm.co.uk>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: GCC 3.1 Released
Date: Thu, 16 May 2002 00:16:00 -0000 [thread overview]
Message-ID: <156580000.1021532418@gandalf.codesourcery.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0205160318390.12287-100000@nicola.brainstorm.co.uk>
> I see no mention of Objective-C improvements.
Thanks for pointing that out.
As a middle manager of sorts, I depend on the information that other
hard-working people prepare. :-)
I read through:
http://gcc.gnu.org/gcc-3.1/changes.html
to compile my list of things to mention, and tried to pick out a
few of the biggest highlights.
Please make sure that for the next release Objective-C gets
mentioned there, and then I will be more likely to see it.
Thank you!
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2002-05-16 7:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 18:48 Mark Mitchell
2002-05-15 19:43 ` Craig Rodrigues
2002-05-15 20:10 ` Joseph S. Myers
2002-05-15 20:17 ` Craig Rodrigues
2002-05-16 1:31 ` Gerald Pfeifer
2002-05-16 6:24 ` Joseph S. Myers
2002-05-16 13:22 ` PATCH for " Gerald Pfeifer
2002-05-15 20:35 ` Nicola Pero
2002-05-15 22:20 ` Zack Weinberg
2002-05-16 0:16 ` Mark Mitchell [this message]
2002-05-16 6:02 ` Nicola Pero
2002-05-16 1:35 ` Gerald Pfeifer
2002-05-16 8:06 ` Kelley Cook
2002-05-16 13:21 ` Gerald Pfeifer
2002-05-15 22:54 ` Robert Schiele
2002-05-16 10:06 ` Janis Johnson
2002-05-16 10:29 ` Robert Schiele
2002-05-16 10:34 ` Janis Johnson
2002-05-16 7:28 ` Richard B. Kreckel
2002-05-16 7:50 ` Mark Mitchell
2002-05-16 8:29 ` Richard B. Kreckel
2002-05-16 11:41 ` Joseph S. Myers
2002-05-16 12:06 ` Joe Buck
2002-05-16 7:49 ` DJ Delorie
2002-05-16 10:38 gcc " aschwarz1309
2002-05-16 22:32 ` Kurt Wall
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=156580000.1021532418@gandalf.codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=nicola@brainstorm.co.uk \
/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).