From: SourceForge.net <no...@so...> - 2005-03-27 17:39:12
|
Feature Requests item #709340, was opened at 2003-03-25 21:33 Message generated for change (Settings changed) made by coldstore You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=360894&aid=709340&group_id=10894 Category: 45. Traces Group: None Status: Open Resolution: None >Priority: 3 Submitted By: Colin McCormack (coldstore) Assigned to: miguel sofer (msofer) Summary: pass more data in array variable trace Initial Comment: 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. ---------------------------------------------------------------------- Comment By: Colin McCormack (coldstore) Date: 2005-03-28 03:36 Message: 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." ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=360894&aid=709340&group_id=10894 |