Re: Do people create parsers for command line arguments?

gah4 <gah4@u.washington.edu>
Fri, 29 Jul 2022 15:30:33 -0700 (PDT)

          From comp.compilers

Related articles
Do people create parsers for command line arguments? costello@mitre.org (Roger L Costello) (2022-07-28)
Re: Do people create parsers for command line arguments? 480-992-1380@kylheku.com (Kaz Kylheku) (2022-07-29)
Re: Do people create parsers for command line arguments? gah4@u.washington.edu (gah4) (2022-07-29)
Re: Do people create parsers for command line arguments? gciofono@gmail.com (Giacinto Cifelli) (2022-08-08)
Re: Do people create parsers for command line arguments? gah4@u.washington.edu (gah4) (2022-08-08)
Re: Do people create parsers for command line arguments? gah4@u.washington.edu (gah4) (2022-08-23)
| List of all articles for this month |

From: gah4 <gah4@u.washington.edu>
Newsgroups: comp.compilers
Date: Fri, 29 Jul 2022 15:30:33 -0700 (PDT)
Organization: Compilers Central
References: 22-07-054 22-07-057
Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="45572"; mail-complaints-to="abuse@iecc.com"
Keywords: parse
Posted-Date: 29 Jul 2022 19:00:18 EDT
In-Reply-To: 22-07-057

On Friday, July 29, 2022 at 2:49:38 PM UTC-7, Kaz Kylheku wrote:


(snip)


> All of these programs must be parsing. They have phrase structures
> and operator precedence with parentheses right the command line.


It seems to me that this is the important part. The simplest processing
of a command line might not count as parsing.


If one processes an arithmetic expression left to right, with no precedence,
that might not count as parsing. Is two different precedence levels enough?


My first thought of the question was for machine generated vs.
hand written parsers. When does it get complicated enough to make
it worth using a parser generator?


Post a followup to this message

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