Tcl Source Code

namespace eval demo {    
    proc foo args {
        puts 0:[info level 0]
        puts 1:[info level -1]
        puts 2:[info level -2]
    }
    variable x
    trace variable x w [namespace code foo]
    proc bar {} {variable x 1}
    bar
}

Output is:

0:foo x {} w
1:
2:bar

Note the [namespace inscope] command
at level 1 is missing.

Logged In: YES 
user_id=80530
Originator: YES


Won't fix in the 8.4.* series.

Logged In: YES 
user_id=80530


marked "knownBug" for 8.4.14

Logged In: YES 
user_id=80530

I know.  The bug fix was
taken back out due to reports
of problems with Itcl.

I've pleaded several times
for examples of these problems,
with none coming.

If I ever get such examples, 
I'll try to understand what
Itcl's needs are, and determine
whether this can be fixed in
a way that still serves them.

If we can't ever get that done,
the test will have to be marked
"knownBug".

Logged In: YES 
user_id=148712

namespace-29.6 fails (again?) in tcl-core-8.4-branch

Logged In: YES 
user_id=80530

I'd like to look into this further.

Is there an Itcl demo script
to get me started?

Logged In: YES 
user_id=72656

Confirmed that this breaks some aspect of itcl, with respect
to tracebacks and/or introspection.  Still examining the
exact cause.

Logged In: YES 
user_id=80530

13:07]tclguyI think this might have borked with itcl
[13:08]tclguywe have a user getting a weird problem with
using itcl with 8.4.13 now (no problem with 8.4.12)
[13:08]tclguyand I've asked them to test an 8.4.13 minus
that patch
[13:08]tclguystill waiting to hear back, but from looking
at itcl, it looks likely suspicious
[13:08]dgpif we must, I don't mind a revert...
[13:08]tclguyitcl does weird stuff with 'namespace
inscope' directly
[13:09]dgp...but it indicates nasty fragility of Itcl

Logged In: YES 
user_id=80530

fixed for 8.4.13 and 8.5a4

File Added - 162735: 1400572-84.patch

Logged In: YES 
user_id=80530


and the patch for 8.4.12....

File Added - 162734: 1400572.patch

Logged In: YES 
user_id=80530


Minimal demo:

 namespace inscope :: {info level 0}

Note this is exactly the same
problem we used to have with
[namespace eval] (545325)

here's the patch...