Overview
Artifact ID: | bcef85f8dfc12d73c886d5b6c9b1e176992f5e16 |
---|---|
Ticket: | 1643952fffffffffffffffffffffffffffffffff
CommRunHook evaluates event hooks twice |
User & Date: | cbascom 2007-01-25 21:58:55 |
Changes
- icomment:
Logged In: YES user_id=1600284 Originator: YES The above description did indeed fix the out of scope variables issue, but I hadn't realized until now that the event hooks were getting evaluated twice. The first time they are evaluated is inside the if/else clause that checks to see whether another interpreter is in use or not. In this case, the uplevel 1 was used when evaluating in the current interpreter so variables were indeed in scope. The same event hook is then evaluated a second time by the eval command just below that if/else clause and at that point the variables are out of scope. I believe the fix is simply to remove that eval.
- login: "cbascom"
- mimetype: "text/plain"
- title changed to: "CommRunHook evaluates event hooks twice"
- username: "cbascom"