On Monday 31 January 2011 08:49 PM, C. Michael Pilato wrote:
On 01/31/2011 10:05 AM, Arwin Arni wrote:
On Monday 31 January 2011 08:01 PM, C. Michael Pilato wrote:
On 01/31/2011 04:48 AM, Arwin Arni wrote:
Should I add parameters for options / values / options& values to decide
the case or shall I use a common parameter for all(sections, options&
values) ?
We generally try to avoid premature over-engineering, and at the moment, we
have no known need for the additional changes you speak of. Introducing
codepaths that we don't exercise can lead to surprise failures later when we
do.
But I am excercising it!
In libsvn_repos/authz.c. I'm using it to make the config population
case-sensitive. (Issue #3781)
Unless I'm mistaken, your immediate need is to make *section* parsing
case-sensitive. Nothing about issue #3781 calls for toggle-able case
handling of options or values. *That's* the "additional changes" stuff I'm
referring to.
Oh! Okay.. It was originally Kamesh's idea to do this.. so.. I guess
I'll have to get back to you after a few more words with him..
Thanks for the feedback..
Regards,
Arwin Arni
