Re: Best language for implementing compilers?

George Neuner <gneuner2@comcast.net>
Sat, 09 Mar 2019 22:47:11 -0500

          From comp.compilers

Related articles
[10 earlier articles]
Re: Best language for implementing compilers? drb@ihatespam.msu.edu (2019-02-19)
Re: Best language for implementing compilers? martin@gkc.org.uk (Martin Ward) (2019-02-19)
Re: Best language for implementing compilers? arnold@skeeve.com (2019-02-20)
Re: Best language for implementing compilers? mertesthomas@gmail.com (2019-03-09)
Re: Best language for implementing compilers? DrDiettrich1@netscape.net (Hans-Peter Diettrich) (2019-03-09)
Re: Best language for implementing compilers? bc@freeuk.com (Bart) (2019-03-09)
Re: Best language for implementing compilers? gneuner2@comcast.net (George Neuner) (2019-03-09)
Re: Best language for implementing compilers? gneuner2@comcast.net (George Neuner) (2019-03-09)
Re: Best language for implementing compilers? 157-073-9834@kylheku.com (Kaz Kylheku) (2019-03-10)
Re: Best language for implementing compilers? 157-073-9834@kylheku.com (Kaz Kylheku) (2019-03-10)
Re: Best language for implementing compilers? christopher.f.clark@compiler-resources.com (Christopher F Clark) (2019-03-10)
Re: Best language for implementing compilers? bc@freeuk.com (Bart) (2019-03-10)
Re: Best language for implementing compilers? DrDiettrich1@netscape.net (Hans-Peter Diettrich) (2019-03-10)
[7 later articles]
| List of all articles for this month |

From: George Neuner <gneuner2@comcast.net>
Newsgroups: comp.compilers
Date: Sat, 09 Mar 2019 22:47:11 -0500
Organization: A noiseless patient Spider
References: 19-02-002 19-02-004 19-02-006 19-03-002 19-03-003
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

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


Post a followup to this message

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