Re: Do people create parsers for command line arguments?

Path	csiph.com!weretis.net!feeder6.news.weretis.net!news.misty.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end
From	gah4 <gah4@u.washington.edu>
Newsgroups	comp.compilers
Subject	Re: Do people create parsers for command line arguments?
Date	Fri, 29 Jul 2022 15:30:33 -0700 (PDT)
Organization	Compilers Central
Lines	16
Sender	news@iecc.com
Approved	comp.compilers@iecc.com
Message-ID	<22-07-059@comp.compilers> (permalink)
References	<22-07-054@comp.compilers> <22-07-057@comp.compilers>
Mime-Version	1.0
Content-Type	text/plain; charset="UTF-8"
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
X-submission-address	compilers@iecc.com
X-moderator-address	compilers-request@iecc.com
X-FAQ-and-archives	http://compilers.iecc.com
In-Reply-To	<22-07-057@comp.compilers>
Xref	csiph.com comp.compilers:3146

Show key headers only | View raw

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?

Thread

csiph-web