Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| [8 earlier articles] |
| Re: Best language for implementing compilers? costello@mitre.org (Costello, Roger L.) (2019-02-12) |
| Re: Best language for implementing compilers? 157-073-9834@kylheku.com (Kaz Kylheku) (2019-02-12) |
| 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) |
| [9 later articles] |
| From: | Hans-Peter Diettrich <DrDiettrich1@netscape.net> |
| Newsgroups: | comp.compilers |
| Date: | Sat, 9 Mar 2019 10:14:01 +0100 |
| Organization: | Compilers Central |
| References: | 19-02-002 19-02-004 19-02-006 19-03-002 |
| Injection-Info: | gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="90489"; mail-complaints-to="abuse@iecc.com" |
| Keywords: | parse |
| Posted-Date: | 09 Mar 2019 20:27:45 EST |
Am 09.03.2019 um 07:47 schrieb mertesthomas@gmail.com:
> For parsing I don't think that pattern matching leads to correct
> results in all cases. I have seen too much buggy attempts to do
> parsing with pattern matching. Even for such simple things as
> lines with key=value I saw "solutions" with pattern matching, that
> triggered bugs when the line was not simple. A good approach for
> parsing is LL(1), which has nothing to do with pattern matching.
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.
DoDi
Return to the
comp.compilers page.
Search the
comp.compilers archives again.