Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| [11 earlier articles] |
| 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) |
| Re: Best language for implementing compilers? gneuner2@comcast.net (George Neuner) (2019-03-10) |
| [6 later articles] |
| From: | George Neuner <gneuner2@comcast.net> |
| Newsgroups: | comp.compilers |
| Date: | Sat, 09 Mar 2019 22:57:25 -0500 |
| Organization: | A noiseless patient Spider |
| 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="39530"; mail-complaints-to="abuse@iecc.com" |
| Keywords: | parse |
| Posted-Date: | 10 Mar 2019 00:22:00 EST |
On Sat, 9 Mar 2019 01:47:38 -0500 (EST), mertesthomas@gmail.com wrote:
>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.
You have seen the approach of bad patterns - you have not seen that
patterns are a bad approach.
I also have seen some poor attempts made using pattern matching - when
the patterns are too general, or don't cover 100% the intended cases -
there will be unintended matches. Pattern matching is only as
exacting as you make it. It doesn't necessarily save you any time or
code ... what it does do is make the code more manageable and easier
to verify.
George
Return to the
comp.compilers page.
Search the
comp.compilers archives again.