public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ziemowit Laski <zlaski@apple.com>
To: gcc mailing list <gcc@gcc.gnu.org>
Cc: Mike Stump <mrs@apple.com>, GNUStep <discuss-gnustep@gnu.org>
Subject: Re: Is ObjC++ still in time for 4.0?
Date: Fri, 19 Nov 2004 00:57:00 -0000	[thread overview]
Message-ID: <3D92B030-39C3-11D9-8317-00039390FFE2@apple.com> (raw)
In-Reply-To: <m2is82okds.fsf@greed.local>

> 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.

> My last comment to Zem was:
>
>> I still don't really know enough, but my best guess is that you
>> should put an extra field in the lang_type structure for C, and in
>> lang_type_class for C++.  Try that and let me know how it goes.

...to which I replied:

   I have two questions/requests:
     (1) Should I add the extra field "unconditionally", i.e., so that 
is is there and unused even for plain C and C+?
     (2) Can you post your response to gcc or gcc-patches, preferrably 
as a response to my last e-mail (see URL above), so that other people
         may chime in?

   Thanks.

...to which Geoff politely retorted:

    (1) Zem, I really don't have time to design this for you.  Please do 
your own work.
    (2) Done.

(For those of you wondering, the above exchange took place within the 
confines of Apple's bug-tracking system.   You'll have to Geoff as to 
why he chose to conduct it there instead of the public FSF list where 
it belongs.)

So, the current status is:
    (a) Geoff has refused to provide an acceptable design;
    (b) Geoff has objected to all other designs presented.

--Zem

  parent reply	other threads:[~2004-11-19  0:37 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 [this message]
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
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=3D92B030-39C3-11D9-8317-00039390FFE2@apple.com \
    --to=zlaski@apple.com \
    --cc=discuss-gnustep@gnu.org \
    --cc=gcc@gcc.gnu.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).