public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: zlaski@apple.com
Cc: discuss-gnustep@gnu.org, gcc@gcc.gnu.org
Subject: Re: Is ObjC++ still in time for 4.0?
Date: Fri, 19 Nov 2004 13:31:00 -0000	[thread overview]
Message-ID: <10411191301.AA28464@vlsi1.ultra.nyu.edu> (raw)

    Since Geoff has objected to every design proposal I made, then
    naturally I was (and am) expecting a constructive alternative.

It would be nice if such a thing could be done, but I don't see it as
a requirement.  It is, after all, your project and what you are
essentially doing is asking for him to do the design for you.

It's true that if somebody doesn't like a design proposal they should be able
to articulate what exactly it is they don't like about it.  I don't believe
Geoff has done that completely, which is a legitimate complaint, but saying
"if you don't like my proposal, make your own" isn't fair: it's not his
project.  On the other hand, I perfectly well understand the difficulty in
articulating what one doesn't like about a proposal.  I've been there many
times: when you're very close to a project, you often get a "gut feeling"
that a patch isn't the right way to do something, but find it very hard to
say exactly why you think that and it can often take a lot of time to figure
it out.

             reply	other threads:[~2004-11-19 12:56 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-19 13:31 Richard Kenner [this message]
2004-11-19 20:22 ` Ziemowit Laski
  -- strict thread matches above, loose matches on Subject: below --
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
2004-11-19 20:08             ` Dave Korn

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=10411191301.AA28464@vlsi1.ultra.nyu.edu \
    --to=kenner@vlsi1.ultra.nyu.edu \
    --cc=discuss-gnustep@gnu.org \
    --cc=gcc@gcc.gnu.org \
    --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).