From: Chuck Robey <chuckr@chuckr.org>
To: Phil Edwards <phil@codesourcery.com>
Cc: gcc@gcc.gnu.org, Helge Hess <helge.hess@opengroupware.org>,
discuss-gnustep@gnu.org
Subject: Re: Is ObjC++ still in time for 4.0?
Date: Mon, 22 Nov 2004 03:22:00 -0000 [thread overview]
Message-ID: <20041121205644.D4002@april.chuckr.org> (raw)
In-Reply-To: <20041119054937.GA3823@disaster.jaj.com>
On Fri, 19 Nov 2004, Phil Edwards wrote:
From a lurker, one who likes objc a lot, is there a written spec on what
the heck is objc++?
I'm worried it's going to bloat my favorite minimalist piece of software.
> On Thu, Nov 18, 2004 at 08:52:44PM -0800, Ziemowit Laski wrote:
> >
> > On 18 Nov 2004, at 20.25, Matt Austern wrote:
> >
> > >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.
> >
> > Yes, some of this "silliness" (although it is symptomatic of things
> > more serious) really should be confined to Apple, although I don't
> > think it is appropriate to take the whole discussion offline
> > altogether. Just as currently Geoff is blocking an approach that Mark
> > and Zack OKed (at least in principle), one could certainly envision
> > Mark, Zack or others objecting to whatever we finally manage to agree
> > upon in Cupertino.
>
> Nobody's proposing that the patch be worked on in stealth, to suddenly
> get checked in from the secret underground Apple labs.
>
> How about the Apple guys take it offline, come up with a design and some
> initial patches, and /then/ bring it back to the lists?
>
>
>
----------------------------------------------------------------------------
Chuck Robey | Interests include C & Java programming, FreeBSD,
chuckr@chuckr.org | electronics, communications, and SF/Fantasy.
New Year's Resolution: I will not sphroxify gullible people into looking up
fictitious words in the dictionary (on the wall at my old fraternity,
Signa Phi Nothing).
----------------------------------------------------------------------------
next prev parent reply other threads:[~2004-11-22 1:31 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 [this message]
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
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=20041121205644.D4002@april.chuckr.org \
--to=chuckr@chuckr.org \
--cc=discuss-gnustep@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=helge.hess@opengroupware.org \
--cc=phil@codesourcery.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).