public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Matz <matz@suse.de>
To: Zack Weinberg <zack@codesourcery.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: A FrontEnd in C++?
Date: Wed, 21 Aug 2002 10:59:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0208211955080.1243-100000@wotan.suse.de> (raw)
In-Reply-To: <20020821174040.GF2803@codesourcery.com>

Hi,

On Wed, 21 Aug 2002, Zack Weinberg wrote:

> > It is far from clear that those problems aren't deficiencies in the
> > GCC's own architecture; any project that would make it possible to use
> > the targetted language as an implementation language for front-ends
> > should be highly encouraged IMSHO.
>
> It seems that many people are more sanguine about allowing front ends
> to be written in their own languages than I am.

Although note, that the initial posting wasn't about adding a new frontend
written in it's own language, but simply written in C++, for which we
already have a frontend.  This has not the usual bootstrap problems.
While this doesn't provide the same testing for the new language, the
maintenace burden of this approach is far less.  Yes we (or better the
developer of that frontend) would need to ensure that he's interfacing
correctly with the backend, but that can be done with a rather small C
part, like e.g. Ada does it.


Ciao,
Michael.

  reply	other threads:[~2002-08-21 10:59 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-17 15:45 khalid aggag
2002-08-17 18:06 ` Michael S. Zick
2002-08-19  0:46 ` Fergus Henderson
2002-08-19  1:02   ` Zack Weinberg
2002-08-19  2:18     ` Gabriel Dos Reis
2002-08-19  2:42       ` Michael S. Zick
2002-08-21 10:40       ` Zack Weinberg
2002-08-21 10:59         ` Michael Matz [this message]
2002-08-21 11:18           ` Zack Weinberg
2002-08-21 11:25             ` Daniel Berlin
2002-08-21 11:35               ` Michael Matz
2002-08-21 11:50                 ` Daniel Berlin
2002-08-22 13:03                   ` Pop Sébastian
2002-08-22 13:11                     ` Diego Novillo
2002-08-22 13:19                       ` Pop Sébastian
2002-08-22 20:19                     ` Daniel Berlin
2002-08-22 12:47                 ` Gabriel Dos Reis
2002-08-21 11:10         ` Phil Edwards
2002-08-21 11:43         ` Ross Smith
2002-08-21 12:24           ` Zack Weinberg
2002-08-22 12:47             ` Gabriel Dos Reis
2002-08-21 21:51         ` Fergus Henderson
2002-08-22 12:47         ` Gabriel Dos Reis
2002-08-22 14:16           ` Zack Weinberg
2002-08-22 15:41             ` Gabriel Dos Reis
2002-08-23  2:20             ` Fergus Henderson
2002-08-23 13:19               ` Toon Moene
2002-08-24  2:25               ` Kai Henningsen
2002-08-19  6:55     ` Alexandre Oliva
2002-08-19  8:50       ` Michael S. Zick
2002-08-19  7:20     ` Diego Novillo
2002-08-19 12:20     ` Mike Stump
2002-08-20  2:19     ` Florian Weimer
2002-08-19 10:51   ` Matt Austern
2002-08-20 11:18 ` Kelley Cook
2002-08-20 11:38   ` Kevin Handy
2002-08-18 14:36 khalid aggag
2002-08-18 15:37 ` Michael S. Zick
2002-08-18 22:48 ` Per Bothner
2002-08-19 16:18 Robert Dewar
2002-08-21 11:41 Robert Dewar
2002-08-21 12:59 ` Geoff Keating
2002-08-21 11:53 Robert Dewar
2002-08-21 12:03 ` Graham Stott
2002-08-21 16:16 ` Zack Weinberg
2002-08-21 11:54 Robert Dewar
2002-08-21 16:19 Richard Kenner
2002-08-22 14:17 ` Zack Weinberg
2002-08-21 16:26 Billinghurst, David (CRTS)
2002-08-21 17:19 Robert Dewar
2002-08-21 17:19 Robert Dewar
2002-08-21 18:00 Richard Kenner
2002-08-22  1:54 Robert Dewar
2002-08-22 13:50 Chris Lattner
2002-08-22 14:53 Robert Dewar
2002-08-22 20:37 ` Geoff Keating
2002-08-22 21:36 ` Hans-Peter Nilsson
2002-08-23  3:08 Robert Dewar
2002-08-24  6:54 Robert Dewar

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=Pine.LNX.4.33.0208211955080.1243-100000@wotan.suse.de \
    --to=matz@suse.de \
    --cc=gcc@gcc.gnu.org \
    --cc=zack@codesourcery.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).