On 4/14/06, Vlad Seryakov <[EMAIL PROTECTED]> wrote: > Yes, i always use Tcl vars but when i have too many different callbacks > and filters, using simple mechanism to access named value that is global > inside the thread make it easier than performing multiple global > statements over the code. If i want to add another var, i need to create > Tcl wrapper so i do not need to go over the code and see where i may use > it, so in this case ns_tls will make it easier. But in general, global > Tcl var is way to go.
If the main motivation is convenience, can't you just write some simple Tcl wrapper around global arrays? A disadvantage of the way you have it now is that everything is stringified before it's stored in the set, and re-objectified on the way out. This is a pretty specialised function. I don't think the core is the right place for it.
