[boost] Re: Re: Re: Re: Formal Review: Command Line & Config library

From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-05-26 07:48:12

Pavol,

>> > L1: option level ( string and boost::any oriented,  defined by
>> > option_description ) L2: typed-paramter level ( represented by
>> > po::parameter function )
>> > 
[...]
>> I completely agree. Basically, this means splitting the current
>> "validator" in two, as your describe above. Plus some polishing of
>> interaction between
>>   'convert'/'interprepter'  -- for string->type conversion
>>   'validator'  -- for checking the value of desired type
>>   'notifier' -- which does storing into local variables
>>
> 
> This sounds very reasonable.
> 
> I would suggest that L2 should be interfacing to variables_map, to allow
> cascading of different input formats formats. I don't know how is this
> feasible though.

Yep, that's right idea.

> 
> Also, typed 'default-value' should be considered as parameter of L2
> definition.

I'll try to.

>> Do you think those levels must be explicitly written down in docs?
> 
> Definitely, logical separation of levels is an important concept of the
> libary. It has to be documented, otherwise users get confused.

OK.

Thanks,
Volodya