Hey folks.
A question or two.
I was reading svn_config.h and noticed that the svn_config_read may be
"de-exported".
<quote>
### Notes: This function, and future ones like it, rather obviates
the need for svn_config_read() and svn_config_merge() as public
interfaces. However, I'm leaving them public for now, until it's
clear they can be de-exported. Hmm, funny how in this context, the
opposite of "exported" is not "imported", eh?
</quote>
Can I/Should I use svn_config and specifically svn_config_read for
repos/fs specifc config files?
If so, can I submit a patch to return a hash of all sections in a
config?
One last thing:
Will I get major grief if I have a config file structure something like
the following: ?
[options_group_a_choice_a]
g_a_opt1 = foo
g_a_opt2 = bar
[options_group_a_choice_b]
g_a_opt1 = bar
g_a_opt2 = foo
[options_group_b_choice_a]
g_b_opt1 = bar
[options_group_b_choice_b]
g_b_opt1 = foo
[uber_group_a]
group_a = options_group_a_choice_b /* section name reference */
group_b = options_group_b_choice_a /* section name reference */
[uber_group_b]
group_a = options_group_a_choice_a /* section name reference */
group_b = options_group_b_choice_b /* section name reference */
Boy I hope this doesn't spark another "xml" vs "ini" incident :-)
Thanks,
gat
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 6 19:21:13 2002