[Tcl-bugs] [ tcl-Bugs-3610404 ] re-resolution gets wrong target

[SourceForge.net <no...@so...>]

Bugs item #3610404, was opened at 2013-04-09 11:57
Message generated for change (Comment added) made by dkf
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=3610404&group_id=10894

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: 35. TclOO Package
Group: current: 8.6.0
Status: Open
Resolution: None
Priority: 9
Private: No
Submitted By: Don Porter (dgp)
Assigned to: Donal K. Fellows (dkf)
Summary: re-resolution gets wrong target

Initial Comment:

Here's the real bug I've been striving to demonstrate,
recording mismatches with exec tracing capability
along the way.

oo::object create foo
oo::objdefine foo {
    method target {} {puts Hit!}
    forward bar my target
    method bump {} {
        set ns [info object namespace ::foo]
        rename ${ns}::my ${ns}::
        rename ${ns}:: ${ns}::my
    }
}
proc harness {} {
    foo target
    foo bar
}
proc handle {cmd args} {
    foo bump
}
trace add execution harness enterstep handle
proc my {method} {
    puts Missed!
}
harness

Output:

Hit!
Missed!

The re-resolution of "my" happens in the wrong
context.

Comparing with the machinery in [tailcall], I think
this one has a simple fix.

----------------------------------------------------------------------

>Comment By: Donal K. Fellows (dkf)
Date: 2013-04-10 02:05

Message:
And that appears to be a bug in Tcl 8.5.

----------------------------------------------------------------------

Comment By: Donal K. Fellows (dkf)
Date: 2013-04-09 13:09

Message:
And the new tests cause a panic under 8.5!

  Tcl_ListObjAppendElement called with shared object

That bumps it right to highest priority.

----------------------------------------------------------------------

Comment By: Donal K. Fellows (dkf)
Date: 2013-04-09 13:02

Message:
Flushing that cache in that way shouldn't cause that. Ick.

----------------------------------------------------------------------

Comment By: Don Porter (dgp)
Date: 2013-04-09 12:04

Message:
Branch bug-3610404 has the one-liner fix.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=3610404&group_id=10894