Re: XPL Analyzer

mac <acolvin@efunct.com>
Thu, 8 Jun 2017 17:13:53 -0000 (UTC)

          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)
Re: XPL Analyzer jamin.hanson@googlemail.com (Ben Hanson) (2017-07-30)
| List of all articles for this month |

From: mac <acolvin@efunct.com>
Newsgroups: comp.compilers
Date: Thu, 8 Jun 2017 17:13:53 -0000 (UTC)
Organization: A noiseless patient Spider
References: 17-06-002 17-06-006 17-06-007
Injection-Info: miucha.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="24076"; mail-complaints-to="abuse@iecc.com"
Keywords: parse
Posted-Date: 09 Jun 2017 11:20:16 EDT

My experience using a port of XPL back in the day was that it generated
these horrible syntax error messages, usually beginning <BOUND HEAD>(...



Post a followup to this message

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