Re: override among command line and config file options

> > So what I proposed was to move as many "inter-option" validation routines
> as possible to a separate interface function which could be called at
> certain points in the application. I mean "inter-option" that it validates
> the relationship between two or more option: group, dependencies, modes just
> to name a few. (I think per option checks, like type, argument needed and
> its type and so on, may remain where it is now.) Actually multiplicity is a
> little bit tricky because if the application deals with multiple sources an
> option can occur more than once in every sources.

> so you suggest to have another function for this, just like the 
> check_required function that can be called from the program, right?

Yeah, something like that.