public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Jose E. Marchesi" <jemarch@es.gnu.org>
To: tstratton@amiriscan.org
Cc: gcc@gnu.org
Subject: Re: Algol Front End
Date: Tue, 07 May 2002 06:57:00 -0000	[thread overview]
Message-ID: <E1755Gh-0000BP-00@termi> (raw)
In-Reply-To: <20020507011444.68EB4F28D1@nile.gnat.com> (dewar@gnat.com)


   A full Algol-68 front end is a huge project. Several person years, it is
   a large and complex language. The definitive reference is the Algol-68
   revised report, published by IFIP (WG2.1). It is a difficult document,
   requiring some considerable facility in reading W grammars.

I would be happy volunteering with the VW grammars for that project. I already
use the Algol 68 'ctrans' implementation, but a gcc front-end would be 
definitly great.

-- 
Jose E. Marchesi    http://es.gnu.org
GNU Spain           http://www.gnu.org

  reply	other threads:[~2002-05-07 13:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-06 18:14 Robert Dewar
2002-05-07  6:57 ` Jose E. Marchesi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-14  7:53 Algol front end Robert Dewar
2002-05-14 11:15 ` Trevor Jenkins
2002-05-09 13:44 Algol Front End Gaius Mulley
2002-05-08 12:15 Algol Front end Robert Dewar
2002-05-08 11:47 Arthur I Schwarz
2002-05-08  1:36 BCD [was Re: Algol front end] Bonzini Paolo
2002-05-14  2:52 ` Algol front end Lars Brinkhoff
2002-05-14  7:02   ` Trevor Jenkins
2002-05-07 20:12 Algol Front End Robert Dewar
2002-05-07 19:53 Algol Front end Robert Dewar
2002-05-07 16:45 Arthur I Schwarz
2002-05-07 15:15 Robert Dewar
2002-05-07  4:47 Robert Dewar
2002-05-07 13:43 ` Tim Josling
2002-05-07  4:29 Tim Josling
2002-05-06 16:54 Algol Front End Tony Stratton
2002-05-06 19:23 ` Scott Robert Ladd
2002-05-07  0:47   ` Steven Bosscher
2002-05-07  7:02 ` Paul Koning

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=E1755Gh-0000BP-00@termi \
    --to=jemarch@es.gnu.org \
    --cc=gcc@gnu.org \
    --cc=tstratton@amiriscan.org \
    /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).