Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!usc!ginosko!uunet!mcsun!hp4nl!nikhefh!n62
From: n62@nikhefh.nikhef.nl (Klamer Schutte)
Newsgroups: comp.os.minix
Subject: Re: Suggested change to ACC compiler
Message-ID: <256@nikhefh.nikhef.nl>
Date: 14 Sep 89 07:59:22 GMT
References: <3196@ast.cs.vu.nl> <531@sirius.ua.oz.au> <1613@draken.nada.kth.se> <3249@ast.cs.vu.nl>
Reply-To: n62@nikhefh.nikhef.nl (Klamer Schutte)
Organization: Nikhef-H, Amsterdam (the Netherlands).
Lines: 23

In article <3249@ast.cs.vu.nl> ast@cs.vu.nl (Andy Tanenbaum) writes:
  ...
>Maybe we could have the current compiler at least accept the new keywords
> const, volatile, and maybe a couple of others, and ignore them.  This
>would at least eliminate -DCONST= etc.
  ...
>Andy Tanenbaum

I think this will be a reasonable compromise (but i like a full ANSI compiler
more :-( ). But i think that besides these semantic isues (which should
include acceptance of prototyping) there should be a tool which checkes
whether the input is really ANSI compatible. This one can be incorporated
in the ATARI compiler; but perhaps this will break the symmetry between the
two frontends.
This tool should allow us to write proper ANSI code; this will keep us up
with the rest of the world.

Comments?

Klamer.
-- 
____________________Yes, mail address changed again :-(_________________________
Klamer Schutte        mcvax!nikhefh!{n62,Schutte}        {Schutte,n62}@nikhef.nl