From: Helge Hess <helge.hess@opengroupware.org>
To: Ziemowit Laski <zlaski@apple.com>
Cc: Mike Stump <mrs@apple.com>, Geoffrey Keating <geoffk@geoffk.org>,
GNUStep <discuss-gnustep@gnu.org>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: Is ObjC++ still in time for 4.0?
Date: Fri, 19 Nov 2004 01:41:00 -0000 [thread overview]
Message-ID: <A5C91B18-39CB-11D9-8CE1-000D936E5072@opengroupware.org> (raw)
In-Reply-To: <3D92B030-39C3-11D9-8317-00039390FFE2@apple.com>
On 19. Nov 2004, at 01:37 Uhr, Ziemowit Laski wrote:
>> Zem is asking me to design his frontend's data structures for him. I
>> don't have time to do that right now, and Zem hasn't done the design
>> work himself, so we're waiting.
> Since Geoff has objected to every design proposal I made, then
> naturally
> I was (and am) expecting a constructive alternative.
So the situation seems to be that you have proposed designs which were
rejected by Geoff, probably because they were either considered
incomplete or unacceptable.
Obviously you can't expect an alternative from him (does he work for
you or Apple?), as he mentions he has the time to review stuff for
inclusion but not to propose designs.
The question for me is how we can resolve the situation to get forward.
Is there any other GCC maintainer besides Geoff who has the authority
to review your proposals for inclusion and to mediate between you two?
In case a theoretical "other" also rejects your proposals, can we find
someone who can come up constructive alternatives people can agree on?
Or maybe Apple can consult (aka pay) Geoff to come up with a
"constructive alternative"?
It would be disappointing if the work on ObjC++ would fail even though
there is someone willing to work on the implementation. We are waiting
_so long_ for that feature ...
best regards,
Helge
--
http://docs.opengroupware.org/Members/helge/
OpenGroupware.org
next prev parent reply other threads:[~2004-11-19 1:38 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 [this message]
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
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=A5C91B18-39CB-11D9-8CE1-000D936E5072@opengroupware.org \
--to=helge.hess@opengroupware.org \
--cc=discuss-gnustep@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@geoffk.org \
--cc=mrs@apple.com \
--cc=zlaski@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).