|Title:||pass more data in array variable trace|
|Submitter:||coldstore||Created on:||2003-03-25 10:33:49|
|Subsystem:||46. Traces||Assigned To:||msofer|
|Status:||Open||Last Modified:||2005-03-28 00:39:11|
Variable traces triggered on arrays are almost completely useless - not enough information is passed to the trace. The attached patch sends the whole array command as the second trace argument (usually the array element in non-array sets, always NULL on array traces.) Although this changes the semantics of trace, it allows array traces to be useful for something. One application is providing array semantics over directories - [array get] can be used as the equivalent of [glob *] Without this change, I can't imagine a use for array variable traces. Colin.
coldstore added on 2005-03-28 00:36:38:
Logged In: YES user_id=19214 I said ''Without this change, I can't imagine a use for array variable traces.''. That was too strong. I should have said "Without this change or something like it, I can't imagine a use for array variable traces."
coldstore added on 2003-03-28 20:51:13:
File Added - 46150: tclVar.diff