[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Command line parsing with genparse
From: |
Alfred M. Szmidt |
Subject: |
Re: Command line parsing with genparse |
Date: |
Wed, 19 Dec 2007 18:11:25 +0100 (CET) |
1. It does a significant part of the work at compile time. So the
generated code can be quite simple and fast.
It is parsing arguments, it doesn't need to be super fast. As for
simplicity, having used argp for alot of things, I all I know is that
getopt/getopt_long are a pain.
2. It is able to auto generate a highly configurable usage
function. Many of the replies on my previous posts to the
coreutils mailing list were about the usage function. argp also
can print a usage function but how far can you customize it?
You can customize as much as you would like.
Has anybody tried to convert one of the coreutils tools to use
argp? I would be very interested to see a comparison to the
genparse solution.
Deberashi converted a bunch of tools in inetutils to use argp instead
of getopt/getopt_long. The thing with getting such a patch considered
for coreutils is that you'd need to convert everything in one go.
Which is alot of work.
- Command line parsing with genparse, Michael Geng, 2007/12/18
- Re: Command line parsing with genparse, Alfred M. Szmidt, 2007/12/18
- Re: Command line parsing with genparse, Michael Geng, 2007/12/18
- Re: Command line parsing with genparse, Alfred M. Szmidt, 2007/12/19
- Re: Command line parsing with genparse, Michael Geng, 2007/12/19
- Re: Command line parsing with genparse, Alfred M. Szmidt, 2007/12/19
- Re: Command line parsing with genparse, Michael Geng, 2007/12/25
- Re: Command line parsing with genparse, Alfred M. Szmidt, 2007/12/27
- Re: Command line parsing with genparse,
Alfred M. Szmidt <=
- Re: Command line parsing with genparse, Alfred M. Szmidt, 2007/12/19
Re: Command line parsing with genparse, Jim Meyering, 2007/12/25