On 23.08.2006, at 17:20, Andrew Piskorski wrote:
That's only necessary to preserve the current ns_config case-insensitivity, right? Wouldn't it be easier to just canonicalize the key values on both write and read? E.g., create a wrapper around nsv which forces all keys to all lowercase. Then the key "Foo_Bar" will be automatically translated to "foo_bar" in all situations.
This is also a posibility I was thinking of. This would work, but then if you would want to generate a dump of the config later on, you would loose the case. If somebody made this: ns_config ns/section/something ns_param MyParam 1 and if we would to re-create the setup in order to put it in the file again, the case would be lost, so the param will not be called "MyParam" but "MYPARAM" or "myparam" whatever case you selected. I do not know if this is/would-be an issue for anybody, but this is important to know. If you ask me: I would go with that and with the nsv as I believe this is most optimal in case of needed work and final result. But I must see that we do not shoot ourselves in the foot by some wrong design decision. Hence so much fuss. Cheers Zoran
