Re: Mini-issue: boolean config values

On Tue, Oct 28, 2003 at 11:01:40PM -0500, Files wrote:
>...
> When you add options, your config_file.c needs to change anyway.

No it doesn't. The config_file just parses stuff and returns it. It
doesn't know anything about the options.

> Therefore you simply add the name of your boolean to it.

Not with Branko's scheme. When you query for an option, you say "what is
the boolean value of this option?" and the config code figures out the
yes/no, true/false, on/off and returns a value. It doesn't know what it is
looking at, other than to interpret the value.

>...
> Duplication occurs where? Seriously, we check for 'yes' and 'no' all over the
> place. I'm not getting the issue unless I'm missing something. The main
> problem is that the config hash takes a string value for a result.

The "yes" and "no" and other strings disappear with Branko's model. You
just ask for the boolean value. No strings at all.

>...
> Somehow I'm not getting it. What I *am* seeing is that this whole 'yes'/'no'
> thing is supposedly supposed to be propagated and repeatedly compared all over
> the place. That's bothering me.

Please look at Branko's code.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org