From: Dan Grillo <dan@grillo.net>
To: Dale Johannesen <dalej@apple.com>,
Matt Austern <austern@apple.com>,
gcc mailing list <gcc@gcc.gnu.org>,
Geoffrey Keating <geoffk@geoffk.org>,
GNUStep <discuss-gnustep@gnu.org>,
Helge Hess <helge.hess@opengroupware.org>,
Mike Stump <mrs@apple.com>, Dale Johannesen <dalej@apple.com>
Subject: Re: Is ObjC++ still in time for 4.0?
Date: Fri, 19 Nov 2004 20:04:00 -0000 [thread overview]
Message-ID: <200411191944.iAJJim8e023425@last.grillo.net> (raw)
In-Reply-To: <926459B3-3A5F-11D9-9965-000A95D7CD40@apple.com>
Organize a lunch and work this out!
--Dan
----- Begin forwarded message:
From: Dale Johannesen <dalej@apple.com>
Sender: discuss-gnustep-bounces+dan_grillo=grillo.net@gnu.org
Subject: Re: Is ObjC++ still in time for 4.0?
To: Matt Austern <austern@apple.com>
Cc: gcc mailing list <gcc@gcc.gnu.org>, Geoffrey Keating <geoffk@geoffk.org>,
GNUStep <discuss-gnustep@gnu.org>, Helge Hess
<helge.hess@opengroupware.org>, Mike Stump <mrs@apple.com>, Dale Johannesen
<dalej@apple.com>
Date: Fri, Nov 19 11:16:53
On Nov 18, 2004, at 8:25 PM, Matt Austern wrote:
> Apple already pays Geoff. Zem, Geoff, and I are all Apple employees.
>
> This discussion should probably happen offline. It's in Apple's
> interest for ObjC++ to get into mainline. It's also in Apple's
> interest to make sure that there aren't any changes that hurt compiler
> performance. It's silly for this discussion to be happening on an
> international email list when most of the people participating in it
> have offices on the same floor of the same building.
Yep. At least it may be educating the people who have the silly idea
Apple is some kind of monolith....
_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnustep
----- End forwarded message
--
Dan Grillo dan@grillo.net 650-299-1470
next prev parent reply other threads:[~2004-11-19 19:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 10:28 Lars Sonchocky-Helldorf
2004-11-17 20:51 ` Mike Stump
2004-11-17 21:53 ` Lars Sonchocky-Helldorf
2004-11-17 22:28 ` Ziemowit Laski
2004-11-17 22:54 ` Gregory John Casamento
2004-11-17 23:02 ` Nicolas Roard
2004-11-17 23:31 ` Joseph S. Myers
2004-11-17 23:17 ` Phil Edwards
2004-11-17 23:50 ` Alex Perez
2004-11-18 0:06 ` Joe Buck
2004-11-18 0:35 ` Gregory John Casamento
2004-11-18 0:46 ` Gregory John Casamento
2004-11-18 0:53 ` Mark Mitchell
2004-11-18 1:18 ` Giovanni Bajo
2004-11-18 23:22 ` Geoffrey Keating
2004-11-18 23:28 ` Gregory John Casamento
2004-11-19 0:57 ` Ziemowit Laski
2004-11-19 1:26 ` Rogelio Serrano
2004-11-19 1:41 ` Helge Hess
2004-11-19 4:26 ` Gregory John Casamento
2004-11-19 5:49 ` Matt Austern
2004-11-19 6:42 ` Ziemowit Laski
2004-11-19 7:52 ` Phil Edwards
2004-11-22 3:22 ` Chuck Robey
2004-11-22 10:07 ` Phil Edwards
2004-11-22 10:31 ` Ranjit Mathew
2004-11-19 19:44 ` Dale Johannesen
2004-11-19 20:04 ` Dan Grillo [this message]
2004-11-19 20:08 ` Dave Korn
2004-11-19 13:31 Richard Kenner
2004-11-19 20:22 ` Ziemowit Laski
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=200411191944.iAJJim8e023425@last.grillo.net \
--to=dan@grillo.net \
--cc=austern@apple.com \
--cc=dalej@apple.com \
--cc=discuss-gnustep@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@geoffk.org \
--cc=helge.hess@opengroupware.org \
--cc=mrs@apple.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).