Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!unixhub!shelby!portia.stanford.edu!earthsea.stanford.edu!gyugyi
From: gyugyi@earthsea.stanford.edu (Paul Gyugyi)
Newsgroups: comp.windows.ms.programmer
Subject: Re: MS Windows compatible YACC and LEX
Keywords: YACC, LEX
Message-ID: <1990Dec7.152136@earthsea.stanford.edu>
Date: 7 Dec 90 23:21:36 GMT
References: <256@stbimbo.UUCP> <28630@usc> <262@stbimbo.UUCP>
Sender: news@portia.Stanford.EDU
Reply-To: gyugyi@earthsea.stanford.edu (Paul Gyugyi)
Organization: Stanford University
Lines: 29

In article <262@stbimbo.UUCP>, ges@stbimbo.UUCP (Gerald Sullivan) writes:

|> Are you linking the parser to your Windows application or just executing
|> the parser from a Windows application as a DOS "process"? I need to do
|> the former.
|> 
...
|> 
|> Thanks,
|> Jerry Sullivan

I'm new to yacc and lex, but maybe this is useful information:
The Actor development system includes a lexical analyzer that works
with YACC output. (or is it lex output?  I'm sorry I don't know
better).  Whatever, the routine you run to generate the tables still
has to run under DOS, and then you take the generated C code and
edit it (with a provided macro) to make it Actor source.  Actor has
a built in something that will take these tables, along with your
input from a command line, and convert it all into actor code which
it then executes.  I think they called it the "data driven lexical
analyzer."

Anyway, I used it to make a small command language for a wargame I'm
writing, which says something about putting powerful tools in the hands
of incompent people :).

--
Paul Gyugyi
gyugyi@earthsea.stanford.edu