There are some refcounting/memory management bugs in command delete
traces.  See [Tcl Bug 811483].

Working on a fix, it seemed worthwhile to compare to the analogous
unset traces for variables, a longer established, more bug-fixed
code base.

The two seemingly analogous operations are opposite in the
expectations they fulfill.

  During a variable unset trace, the traced variable is already
  unset, but the trace has the power to recreate it.
  
  During a command delete trace, the traced command still exists,
  but will be deleted following the trace, and the trace can't do
  anything to stop it.
  
Is there an intentional design reason behind these differences?  Can
someone explain it?

Are there users of command delete traces that depend on these
details?

| Don Porter          Mathematical and Computational Sciences Division |
| donald.porter@[...].gov             Information Technology Laboratory |
| http://math.nist.gov/~DPorter/                                  NIST |
|______________________________________________________________________|



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tcl-Core mailing list
Tcl-Core@[...].net
https://lists.sourceforge.net/lists/listinfo/tcl-core