[cvs] bogofilter/src bogoconfig.c,1.136,1.137 configfile.c,1.33,1.34 configfile.h,1.10,1.11
Stefan Bellon
sbellon at sbellon.de
Sun Jan 18 21:36:22 CET 2004
- Previous message (by thread): [cvs] bogofilter/src bogoconfig.c,1.136,1.137 configfile.c,1.33,1.34 configfile.h,1.10,1.11
- Next message (by thread): [cvs] bogofilter/src bogoconfig.c,1.136,1.137 configfile.c,1.33,1.34 configfile.h,1.10,1.11
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Matthias Andree wrote:
> On Sat, 17 Jan 2004, relson at users.sourceforge.net wrote:
[snip]
> > Add '--option=value' to permit config file options on the command
> > line.
> >
> > + case '-':
> > + process_config_option(optarg, true, PR_COMMAND);
> > + break;
> > +
> Is this the right thing to do? I doubt it. I'd think we'd use
> gnugetopt to parse "--option"s and use a dedicated option (yes, yet
> another) to expose configuration file options.
So, why not use '-' as the dedicated option that tells that now a
configuration file option follows? The first '-' is the command line
switch and the second '-' is your dedicated option. What's wrong with
that?
--
Stefan Bellon
- Previous message (by thread): [cvs] bogofilter/src bogoconfig.c,1.136,1.137 configfile.c,1.33,1.34 configfile.h,1.10,1.11
- Next message (by thread): [cvs] bogofilter/src bogoconfig.c,1.136,1.137 configfile.c,1.33,1.34 configfile.h,1.10,1.11
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the bogofilter-dev
mailing list