Description binoctex 2010-01-26 22:58:52 EST

Build Identifier: M20090917-0800

When a function is set as the value of a variable
eg.:

proc foo {a b} {
   puts "$a $b"
}

set myProc foo <-- pressing F3 on foo does not work

set arga   "bar"
set argb   "baz"

executeStep $myProc $arga $argb

The open declaration will not work unless it is enclosed in execution brackets[] or used to start a new line of code.

In the example I have shown here, the name of the procedure is to be passed in as an argument to another procedure.  
Our current TCL environment has on the order of 5,000 files using this format. (this is for tracking and reporting step level details for all execution of code).

For our particular environment the severity is MAJOR as this has a huge impact as our code declarations are inaccessible.

Reproducible: Always

Steps to Reproduce:
1. create a valid procedure
2. set it as the value of a variable
3. mouseover the value from step 2 and press F3