From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-0.0 required=3.0 tests=BAYES_20 autolearn=ham
	autolearn_force=no version=3.4.5-pre1
Date: 9 Jun 93 22:51:00 GMT
From: enterpoop.mit.edu!news.kei.com!sol.ctr.columbia.edu!emory!swrinde!menudo.
uh.edu!cl2.cl.uh.edu!swen09d2@ucbvax.Berkeley.EDU  (440722148 DUGAN, TIMOTHY R)
Subject: Re: AFLEX/AYACC on WUARCHIVE
Message-ID: <9JUN199316515213@cl2.cl.uh.edu>
List-Id: <comp.lang.ada>

In article <conn.739591842@wuarchive.wustl.edu>, conn@wuarchive.wustl.edu (Rich
ard Conn) writes...
> 
>Release Notice
>Release of: AFLEX/AYACC 1.3a
>------------------------------
>1. Taxonomy:
>    SOFTWARE DEVELOPMENT TOOLS
>        PARSER GENERATOR
>            AFLEX AND AYACC
>------------------------------
> . . .

Do you still produce ALEX?  I had a problem with AFLEX in that it
had to get its input from text_io.  This brings up a question . . .

Why don't tools like AFLEX generate Ada generics?  That way, the 
user can provide the I/O functions:

with xx.token_type;
generic
   with function get_character return character;
   with procedure unget_character(char : in character);
   . . .
function yylex return xx.token_type;