public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@markmitchell.com>
To: jbuck@synopsys.com
Cc: Jan.Madsen@epfl.ch, egcs@cygnus.com, jason@cygnus.com
Subject: Re: Patch for sC++ to GNU C++.
Date: Thu, 22 Oct 1998 11:32:00 -0000	[thread overview]
Message-ID: <199810221459.HAA05879@smtp.earthlink.net> (raw)
In-Reply-To: <199810211938.MAA12692@atrus.synopsys.com>

>>>>> "Joe" == Joe Buck <jbuck@synopsys.com> writes:

    Joe> The idea is that there would be a new directory gcc/sc which
    Joe> would be a peer of gcc/cp.  It would contain all of the new
    Joe> sc-xxx.c files.  Initially, the parser would need to be
    Joe> duplicated and modified, which I don't much like.

Me neither.  In fact, I'm thinking about how to (partially) reunify
the C and C++ front-ends.  Please, let's not duplicate any more code.

-- 
Mark Mitchell 			mark@markmitchell.com
Mark Mitchell Consulting	http://www.markmitchell.com

  reply	other threads:[~1998-10-22 11:32 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 [this message]
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
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=199810221459.HAA05879@smtp.earthlink.net \
    --to=mark@markmitchell.com \
    --cc=Jan.Madsen@epfl.ch \
    --cc=egcs@cygnus.com \
    --cc=jason@cygnus.com \
    --cc=jbuck@synopsys.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).