From: Joe Buck <jbuck@synopsys.com>
To: mark@markmitchell.com (Mark Mitchell)
Cc: jbuck@synopsys.com, Jan.Madsen@epfl.ch, egcs@cygnus.com,
jason@cygnus.com
Subject: Re: Patch for sC++ to GNU C++.
Date: Thu, 22 Oct 1998 21:15:00 -0000 [thread overview]
Message-ID: <199810221819.LAA06205@atrus.synopsys.com> (raw)
In-Reply-To: <199810221755.KAA23002@smtp.earthlink.net>
>
> >>>>> "Joe" == Joe Buck <jbuck@Synopsys.COM> writes:
>
> Joe> Please cd to gcc/objc and look around. Do you see
> Joe> duplication? No, you only see six source files. The only
> Joe> duplication is in objc-parse.y: it and c-parse.y are both
> Joe> obtained from c-parse.in.
Mark writes:
> I agree with you. Thank you for making me pay attention long enough
> to see what was really going on.
Convergence may be possible. :-)
So, Jan, I guess what I am asking is for you to restructure your patch so
that it looks like the way objc is built on top of C. If I understand
things correctly, only the bison input needs changing, right, so it is
analogous to Objective-C?
(I can't promise, of course, that your changes would then be accepted,
that's up to Jason and Jeff -- but it would make it more likely, I think).
next prev parent reply other threads:[~1998-10-22 21:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-21 3:27 Jan Madsen
1998-10-21 19:20 ` Joe Buck
1998-10-22 11:32 ` Mark Mitchell
1998-10-22 18:00 ` Joe Buck
1998-10-22 21:15 ` Jan Madsen
1998-10-22 22:22 ` Mark Mitchell
1998-10-22 18:00 ` Joe Buck
1998-10-22 13:59 ` Mark Mitchell
1998-10-22 21:15 ` Joe Buck [this message]
1998-10-23 4:36 ` Jan Madsen
1998-10-25 13:53 ` Jeffrey A Law
1998-10-22 21:15 ` Chip Salzenberg
1998-10-21 22:10 ` Mark Mitchell
[not found] ` <199810212214.PAA16044.cygnus.egcs@smtp.earthlink.net>
1998-10-22 22:22 ` Jason Merrill
1998-10-25 18:03 ` Ken Raeburn
1998-10-22 13:59 Mike Stump
1998-11-13 5:01 Jan Madsen
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=199810221819.LAA06205@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=Jan.Madsen@epfl.ch \
--cc=egcs@cygnus.com \
--cc=jason@cygnus.com \
--cc=mark@markmitchell.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).