Path: csiph.com!3.us.feeder.erje.net!feeder.erje.net!news.linkpendium.com!news.linkpendium.com!news.snarked.org!border2.nntp.dca1.giganews.com!nntp.giganews.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end
From: George Neuner <gneuner2@comcast.net>
Newsgroups: comp.compilers
Subject: Re: Best language for implementing compilers?
Date: Sat, 09 Mar 2019 22:47:11 -0500
Organization: A noiseless patient Spider
Lines: 10
Sender: news@iecc.com
Approved: comp.compilers@iecc.com
Message-ID: <19-03-005@comp.compilers>
References: <19-02-002@comp.compilers> <19-02-004@comp.compilers> <19-02-006@comp.compilers> <19-03-002@comp.compilers> <19-03-003@comp.compilers>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="39014"; mail-complaints-to="abuse@iecc.com"
Keywords: parse
Posted-Date: 10 Mar 2019 00:20:04 EST
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:2171

On Sat, 9 Mar 2019 10:14:01 +0100, Hans-Peter Diettrich
<DrDiettrich1@netscape.net> wrote:

>IMO bottom-up parsers (LR) do pattern matching, in contrast to top-down
>parsers (LL). Where bottom-up parsers can suffer from shift/reduce
>conflicts.

And top-down parsers suffer from common prefixes and backtracking.

George