Re: XPL Analyzer

George Neuner <gneuner2@comcast.net>
Mon, 05 Jun 2017 22:17:16 -0400

          From comp.compilers

Related articles
XPL Analyzer shoefoot@gmail.com (Shoefoot) (2017-06-05)
Re: XPL Analyzer robin51@dodo.com.au (Robin Vowels) (2017-06-05)
Re: XPL Analyzer gneuner2@comcast.net (George Neuner) (2017-06-05)
Re: XPL Analyzer shoefoot@gmail.com (Shoefoot) (2017-06-07)
Re: XPL Analyzer acolvin@efunct.com (mac) (2017-06-08)
Re: XPL Analyzer slkpg4@gmail.com (SLK Parser Generator) (2017-06-09)
Re: XPL Analyzer gneuner2@comcast.net (George Neuner) (2017-06-09)
Re: XPL Analyzer DrDiettrich1@aol.com.dmarc.email (Hans-Peter Diettrich) (2017-06-13)
| List of all articles for this month |

From: George Neuner <gneuner2@comcast.net>
Newsgroups: comp.compilers
Date: Mon, 05 Jun 2017 22:17:16 -0400
Organization: A noiseless patient Spider
References: 17-06-002
Injection-Info: miucha.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="41990"; mail-complaints-to="abuse@iecc.com"
Keywords: parse, history
Posted-Date: 07 Jun 2017 18:37:18 EDT

On Mon, 5 Jun 2017 01:48:30 -0400 (EDT), Shoefoot <shoefoot@gmail.com>
wrote:


>I am in the process of writing an XPL compiler. This is the
>language defined by McKeeman in his book "A Compiler Generator".
>While searching the net I have found some references to a version
>of the XPL Analyzer that used LALR(1) parse tables. Does anyone
>have source code for such a program?


I'm not sure I understand your question: do you have existing tables
that you'd like to plug in to a parser tool, or are you looking for
the (E)BNF source needed to generate tables?


There are some parser tools, e.g., Gold (http://goldparser.org), that
separate the tables and actions from the "engine" that executes them,
and that can demand load new table/action sets.


However, I'm not aware of any tool that can directly use pre-existing
"foreign" tables ... every tool I know of has to have generated the
tables itself.


George


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.