Command line argument parsing in Bayonne is non-standard

Hello,

I am Antonio Diaz, maintainer of some GNU packages.

I have noticed that Bayonne's code for parsing command line
arguments 
lacks some features of POSIX and GNU standards. For example,
short 
options can't be grouped, long option names have to be
complete 
(unambiguous prefixes are rejected), etc.

I have written Arg_parser, a parser class for command line
arguments 
that is both safe and easy to use. Arg_parser does not use
the functions 
getopt nor getopt_long, and avoids all their inconvenients.
For example, 
  it does not use global variables, you no more have to
maintain a 
long_options struct and a separated options string, etc.

At least four GNU programs are currently using Arg_parser,
and I expect 
this number to grow soon.

Here http
s://savannah.nongnu.org/projects/arg-parser/ you can
find a 
description of Arg_parser. If you like it, you may use it in
Bayonne or 
any other project. If you need help switching to Arg_parser,
I can send 
you a patch for bayonne2-2.3.2.


Regards,
Antonio.



_______________________________________________
Bayonne-devel mailing list
Bayonne-develgnu.org
h
ttp://lists.gnu.org/mailman/listinfo/bayonne-devel

This needed to be updated anyway since I think some of our
options are 
no longer consistent with other GNU programs, and this is a
good time to 
look at this.  You might also like to look at the new
sipwitch codebase. 
    Maybe audiotool (from GNU ccaudio) should also be
revised.

Antonio Diaz Diaz wrote:
> Hello,
> 
> I am Antonio Diaz, maintainer of some GNU packages.
> 
> I have noticed that Bayonne's code for parsing command
line arguments 
> lacks some features of POSIX and GNU standards. For
example, short 
> options can't be grouped, long option names have to be
complete 
> (unambiguous prefixes are rejected), etc.
> 
> I have written Arg_parser, a parser class for command
line arguments 
> that is both safe and easy to use. Arg_parser does not
use the functions 
> getopt nor getopt_long, and avoids all their
inconvenients. For example, 
>  it does not use global variables, you no more have to
maintain a 
> long_options struct and a separated options string,
etc.
> 
> At least four GNU programs are currently using
Arg_parser, and I expect 
> this number to grow soon.
> 
> Here http
s://savannah.nongnu.org/projects/arg-parser/ you can
find a 
> description of Arg_parser. If you like it, you may use
it in Bayonne or 
> any other project. If you need help switching to
Arg_parser, I can send 
> you a patch for bayonne2-2.3.2.
> 
> 
> Regards,
> Antonio.
> 
> 
> 
> _______________________________________________
> Bayonne-devel mailing list
> Bayonne-develgnu.org
> h
ttp://lists.gnu.org/mailman/listinfo/bayonne-devel

_______________________________________________
Bayonne-devel mailing list
Bayonne-develgnu.org
h
ttp://lists.gnu.org/mailman/listinfo/bayonne-devel