On 8/23/06, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
On 23.08.2006, at 18:35, Mike wrote: > I do have one concern with this change - what happens when the value > (where case must be preserved) for some key is actually the name of > another section or key? I do not have enough experience to tell if > this is ever a problem, but I am not sure how this situation would be > handled. Perhaps by the code that uses that config value? Hm... this does not compute. If we look at the how nsv's would replace the existing ns_set as backend for storage: each ns_section would receive a separate nsv_array, so to speak. In details, this would be handled on the C instead of Tcl level, but it can be described this way for simplicity.
ns_section ns/one ns_param look_in_section "Two" ns_section ns/two ns_param look_for_me "value" "Two" has to remain with-case because it is a value, but its intent is to point the reader of the config at ns/two, which is now lowercased.
