Path: csiph.com!feeder.erje.net!2.us.feeder.erje.net!weretis.net!feeder6.news.weretis.net!feeder.usenetexpress.com!feeder1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end From: "SLK Parser Generator" Newsgroups: comp.compilers Subject: Re: XPL Analyzer Date: Fri, 09 Jun 2017 08:38:05 -0800 Organization: SLK Systems Lines: 13 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <17-06-010@comp.compilers> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes Content-Transfer-Encoding: 8bit Injection-Info: miucha.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="24216"; mail-complaints-to="abuse@iecc.com" Keywords: parse, history Posted-Date: 09 Jun 2017 11:20:41 EDT X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: csiph.com comp.compilers:1891 From https://en.wikipedia.org/wiki/XPL "XCOM and XA were subsequently changed to instead use a variant of Donald Knuth's LR parser bottom-up method.[4] XCOM's variant is called Simple LR or SLR. It handles more grammars than MSP but not quite as many grammars as LALR or full LR(1). The differences from LR(1) are mostly in the table generator's algorithms, not in the compile-time parser method. XCOM and XA predate the widespread availability of Unix and its yacc parser generator tool. XA and yacc have similar purposes." I would suggest using LR, given the power of today's hardware. SLK generates LR(k) and it was much easier for me to implement than the LALR(k) that is also supported.