Re: Do people create parsers for command line arguments?

in general the linux command line arguments are parsed through getopt(3)
https://www.man7.org/linux/man-pages/man3/getopt.3.html


and it is better not to implement special things on the command line,
because it could be pre-parsed or expanded by the shell itself.


then if you want to pass a string on the command line, that is
different, but then again, it is better to take it from stdin.


On Sat, Jul 30, 2022 at 1:00 AM gah4 <gah4@u.washington.edu> wrote:
>
> 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?

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