From: SourceForge.net <no...@so...> - 2006-02-27 20:03:12
|
Bugs item #1439836, was opened at 2006-02-27 14:21 Message generated for change (Comment added) made by dgp You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1439836&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: 44. Parsing and Eval >Group: current: 8.4.12 Status: Open Resolution: None Priority: 5 Submitted By: Don Porter (dgp) >Assigned to: Don Porter (dgp) >Summary: TCL_EVAL_GLOBAL vs. [uplevel #0] Initial Comment: The flag TCL_EVAL_GLOBAL ought to have identical impact as [uplevel #0], but these tests demo they are different when exec traces are present: test trace-21.9 {trace execution: TCL_EVAL_GLOBAL} { trace add execution foo enter soom proc ::soom args {lappend ::info SUCCESS [info level]} set ::info {} namespace eval test_ns_1 { proc soom args {lappend ::info FAIL [info level]} # [testevalobjv 1 ...] ought to produce the same # results as [uplevel #0 ...]. testevalobjv 1 foo x uplevel #0 foo x } namespace delete test_ns_1 trace remove execution foo enter soom set ::info } {SUCCESS 1 SUCCESS 1} test trace-21.10 {trace execution: TCL_EVAL_GLOBAL} { trace add execution foo leave soom proc ::soom args {lappend ::info SUCCESS [info level]} set ::info {} namespace eval test_ns_1 { proc soom args {lappend ::info FAIL [info level]} # [testevalobjv 1 ...] ought to produce the same # results as [uplevel #0 ...]. testevalobjv 1 foo x uplevel #0 foo x } namespace delete test_ns_1 trace remove execution foo leave soom set ::info } {SUCCESS 1 SUCCESS 1} ---------------------------------------------------------------------- >Comment By: Don Porter (dgp) Date: 2006-02-27 15:03 Message: Logged In: YES user_id=80530 This additional test demos similar trouble with [::unknown]: test parse-8.10 {Tcl_EvalObjv procedure, TCL_EVAL_GLOBAL} testevalobjv { rename ::unknown unknown.save proc ::unknown args {lappend ::info [info level]} catch {rename ::noSuchCommand {}} set ::info {} namespace eval test_ns_1 { testevalobjv 1 noSuchCommand uplevel #0 noSuchCommand } namespace delete test_ns_1 rename ::unknown {} rename unknown.save ::unknown set ::info } {1 1} ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1439836&group_id=10894 |
From: SourceForge.net <no...@so...> - 2006-02-27 22:45:49
|
Bugs item #1439836, was opened at 2006-02-27 14:21 Message generated for change (Comment added) made by dgp You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1439836&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: 44. Parsing and Eval Group: current: 8.4.12 Status: Open Resolution: None Priority: 5 Submitted By: Don Porter (dgp) Assigned to: Don Porter (dgp) Summary: TCL_EVAL_GLOBAL vs. [uplevel #0] Initial Comment: The flag TCL_EVAL_GLOBAL ought to have identical impact as [uplevel #0], but these tests demo they are different when exec traces are present: test trace-21.9 {trace execution: TCL_EVAL_GLOBAL} { trace add execution foo enter soom proc ::soom args {lappend ::info SUCCESS [info level]} set ::info {} namespace eval test_ns_1 { proc soom args {lappend ::info FAIL [info level]} # [testevalobjv 1 ...] ought to produce the same # results as [uplevel #0 ...]. testevalobjv 1 foo x uplevel #0 foo x } namespace delete test_ns_1 trace remove execution foo enter soom set ::info } {SUCCESS 1 SUCCESS 1} test trace-21.10 {trace execution: TCL_EVAL_GLOBAL} { trace add execution foo leave soom proc ::soom args {lappend ::info SUCCESS [info level]} set ::info {} namespace eval test_ns_1 { proc soom args {lappend ::info FAIL [info level]} # [testevalobjv 1 ...] ought to produce the same # results as [uplevel #0 ...]. testevalobjv 1 foo x uplevel #0 foo x } namespace delete test_ns_1 trace remove execution foo leave soom set ::info } {SUCCESS 1 SUCCESS 1} ---------------------------------------------------------------------- >Comment By: Don Porter (dgp) Date: 2006-02-27 17:45 Message: Logged In: YES user_id=80530 here's a patch with the tests and the fix. ---------------------------------------------------------------------- Comment By: Don Porter (dgp) Date: 2006-02-27 15:03 Message: Logged In: YES user_id=80530 This additional test demos similar trouble with [::unknown]: test parse-8.10 {Tcl_EvalObjv procedure, TCL_EVAL_GLOBAL} testevalobjv { rename ::unknown unknown.save proc ::unknown args {lappend ::info [info level]} catch {rename ::noSuchCommand {}} set ::info {} namespace eval test_ns_1 { testevalobjv 1 noSuchCommand uplevel #0 noSuchCommand } namespace delete test_ns_1 rename ::unknown {} rename unknown.save ::unknown set ::info } {1 1} ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1439836&group_id=10894 |
From: SourceForge.net <no...@so...> - 2006-02-27 23:49:15
|
Bugs item #1439836, was opened at 2006-02-27 14:21 Message generated for change (Comment added) made by dgp You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1439836&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: 44. Parsing and Eval Group: current: 8.4.12 Status: Open Resolution: None Priority: 5 Submitted By: Don Porter (dgp) Assigned to: Don Porter (dgp) Summary: TCL_EVAL_GLOBAL vs. [uplevel #0] Initial Comment: The flag TCL_EVAL_GLOBAL ought to have identical impact as [uplevel #0], but these tests demo they are different when exec traces are present: test trace-21.9 {trace execution: TCL_EVAL_GLOBAL} { trace add execution foo enter soom proc ::soom args {lappend ::info SUCCESS [info level]} set ::info {} namespace eval test_ns_1 { proc soom args {lappend ::info FAIL [info level]} # [testevalobjv 1 ...] ought to produce the same # results as [uplevel #0 ...]. testevalobjv 1 foo x uplevel #0 foo x } namespace delete test_ns_1 trace remove execution foo enter soom set ::info } {SUCCESS 1 SUCCESS 1} test trace-21.10 {trace execution: TCL_EVAL_GLOBAL} { trace add execution foo leave soom proc ::soom args {lappend ::info SUCCESS [info level]} set ::info {} namespace eval test_ns_1 { proc soom args {lappend ::info FAIL [info level]} # [testevalobjv 1 ...] ought to produce the same # results as [uplevel #0 ...]. testevalobjv 1 foo x uplevel #0 foo x } namespace delete test_ns_1 trace remove execution foo leave soom set ::info } {SUCCESS 1 SUCCESS 1} ---------------------------------------------------------------------- >Comment By: Don Porter (dgp) Date: 2006-02-27 18:49 Message: Logged In: YES user_id=80530 revised patch ---------------------------------------------------------------------- Comment By: Don Porter (dgp) Date: 2006-02-27 17:45 Message: Logged In: YES user_id=80530 here's a patch with the tests and the fix. ---------------------------------------------------------------------- Comment By: Don Porter (dgp) Date: 2006-02-27 15:03 Message: Logged In: YES user_id=80530 This additional test demos similar trouble with [::unknown]: test parse-8.10 {Tcl_EvalObjv procedure, TCL_EVAL_GLOBAL} testevalobjv { rename ::unknown unknown.save proc ::unknown args {lappend ::info [info level]} catch {rename ::noSuchCommand {}} set ::info {} namespace eval test_ns_1 { testevalobjv 1 noSuchCommand uplevel #0 noSuchCommand } namespace delete test_ns_1 rename ::unknown {} rename unknown.save ::unknown set ::info } {1 1} ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1439836&group_id=10894 |
From: SourceForge.net <no...@so...> - 2006-02-27 23:56:23
|
Bugs item #1439836, was opened at 2006-02-27 14:21 Message generated for change (Comment added) made by dgp You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1439836&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: 44. Parsing and Eval Group: current: 8.4.12 Status: Open Resolution: None Priority: 5 Submitted By: Don Porter (dgp) Assigned to: Don Porter (dgp) Summary: TCL_EVAL_GLOBAL vs. [uplevel #0] Initial Comment: The flag TCL_EVAL_GLOBAL ought to have identical impact as [uplevel #0], but these tests demo they are different when exec traces are present: test trace-21.9 {trace execution: TCL_EVAL_GLOBAL} { trace add execution foo enter soom proc ::soom args {lappend ::info SUCCESS [info level]} set ::info {} namespace eval test_ns_1 { proc soom args {lappend ::info FAIL [info level]} # [testevalobjv 1 ...] ought to produce the same # results as [uplevel #0 ...]. testevalobjv 1 foo x uplevel #0 foo x } namespace delete test_ns_1 trace remove execution foo enter soom set ::info } {SUCCESS 1 SUCCESS 1} test trace-21.10 {trace execution: TCL_EVAL_GLOBAL} { trace add execution foo leave soom proc ::soom args {lappend ::info SUCCESS [info level]} set ::info {} namespace eval test_ns_1 { proc soom args {lappend ::info FAIL [info level]} # [testevalobjv 1 ...] ought to produce the same # results as [uplevel #0 ...]. testevalobjv 1 foo x uplevel #0 foo x } namespace delete test_ns_1 trace remove execution foo leave soom set ::info } {SUCCESS 1 SUCCESS 1} ---------------------------------------------------------------------- >Comment By: Don Porter (dgp) Date: 2006-02-27 18:56 Message: Logged In: YES user_id=80530 here's the corresponding patch for the HEAD ---------------------------------------------------------------------- Comment By: Don Porter (dgp) Date: 2006-02-27 18:49 Message: Logged In: YES user_id=80530 revised patch ---------------------------------------------------------------------- Comment By: Don Porter (dgp) Date: 2006-02-27 17:45 Message: Logged In: YES user_id=80530 here's a patch with the tests and the fix. ---------------------------------------------------------------------- Comment By: Don Porter (dgp) Date: 2006-02-27 15:03 Message: Logged In: YES user_id=80530 This additional test demos similar trouble with [::unknown]: test parse-8.10 {Tcl_EvalObjv procedure, TCL_EVAL_GLOBAL} testevalobjv { rename ::unknown unknown.save proc ::unknown args {lappend ::info [info level]} catch {rename ::noSuchCommand {}} set ::info {} namespace eval test_ns_1 { testevalobjv 1 noSuchCommand uplevel #0 noSuchCommand } namespace delete test_ns_1 rename ::unknown {} rename unknown.save ::unknown set ::info } {1 1} ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1439836&group_id=10894 |
From: SourceForge.net <no...@so...> - 2006-02-28 15:49:49
|
Bugs item #1439836, was opened at 2006-02-27 14:21 Message generated for change (Comment added) made by dgp You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1439836&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: 44. Parsing and Eval Group: current: 8.4.12 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Don Porter (dgp) Assigned to: Don Porter (dgp) Summary: TCL_EVAL_GLOBAL vs. [uplevel #0] Initial Comment: The flag TCL_EVAL_GLOBAL ought to have identical impact as [uplevel #0], but these tests demo they are different when exec traces are present: test trace-21.9 {trace execution: TCL_EVAL_GLOBAL} { trace add execution foo enter soom proc ::soom args {lappend ::info SUCCESS [info level]} set ::info {} namespace eval test_ns_1 { proc soom args {lappend ::info FAIL [info level]} # [testevalobjv 1 ...] ought to produce the same # results as [uplevel #0 ...]. testevalobjv 1 foo x uplevel #0 foo x } namespace delete test_ns_1 trace remove execution foo enter soom set ::info } {SUCCESS 1 SUCCESS 1} test trace-21.10 {trace execution: TCL_EVAL_GLOBAL} { trace add execution foo leave soom proc ::soom args {lappend ::info SUCCESS [info level]} set ::info {} namespace eval test_ns_1 { proc soom args {lappend ::info FAIL [info level]} # [testevalobjv 1 ...] ought to produce the same # results as [uplevel #0 ...]. testevalobjv 1 foo x uplevel #0 foo x } namespace delete test_ns_1 trace remove execution foo leave soom set ::info } {SUCCESS 1 SUCCESS 1} ---------------------------------------------------------------------- >Comment By: Don Porter (dgp) Date: 2006-02-28 10:49 Message: Logged In: YES user_id=80530 Patches committed. Bug fixed for 8.4.13 and 8.5a4. ---------------------------------------------------------------------- Comment By: Don Porter (dgp) Date: 2006-02-27 18:56 Message: Logged In: YES user_id=80530 here's the corresponding patch for the HEAD ---------------------------------------------------------------------- Comment By: Don Porter (dgp) Date: 2006-02-27 18:49 Message: Logged In: YES user_id=80530 revised patch ---------------------------------------------------------------------- Comment By: Don Porter (dgp) Date: 2006-02-27 17:45 Message: Logged In: YES user_id=80530 here's a patch with the tests and the fix. ---------------------------------------------------------------------- Comment By: Don Porter (dgp) Date: 2006-02-27 15:03 Message: Logged In: YES user_id=80530 This additional test demos similar trouble with [::unknown]: test parse-8.10 {Tcl_EvalObjv procedure, TCL_EVAL_GLOBAL} testevalobjv { rename ::unknown unknown.save proc ::unknown args {lappend ::info [info level]} catch {rename ::noSuchCommand {}} set ::info {} namespace eval test_ns_1 { testevalobjv 1 noSuchCommand uplevel #0 noSuchCommand } namespace delete test_ns_1 rename ::unknown {} rename unknown.save ::unknown set ::info } {1 1} ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1439836&group_id=10894 |