From: Bernd S. <ber...@in...> - 2007-10-01 06:12:29
|
On Sun, 30 Sep 2007 22:25:58 +0200, Colin Adams = <col...@ho...> wrote: >> I am thinking about adding an optional >> 'split character' to AP_OPTION_WITH_PARAMETER that make '--foo=3Dx,y'= >> equivalent to '--foo=3Dx --foo=3Dy'. > > I suppose that will do (assuming the split character is configurable).= After having slept for a night, I think this is design overkill. Just = developing a special option type should be sufficient. >> Also, I have strengthend the preconditions for parsing, and now you = >> should >> have a contract violation if you add "two options with the same short= or >> long form" (it is a little more complicated with alternative options >> lists). The tag of the exception is currently 'valid_options', which = is >> not too good, but difficult to change. > > Is it committed yet? I will try it out when it is. I has been committed and already been reviewed by Eric (thanks, do you = never sleep? ;-) ) >> PPS: I still have the request open to have `mutually exclusive option= s', >> but I have not found a good solution yet. > > Can't you just have references to other options which are to be regard= ed = > as mutually exclusive? The problem is not the check itself, but - where to configure it (parser or option) - how to generate a nice help text format illustrating it Bernd |