Tony,
>I have a seperate tcl script with a bunch of procedures in it; if I
>source the tcl file in the init procedure, all of the code gets sucked
>into the vtcl-generated script.
I am doing a very similar thing and it works just fine.
What I have found is that VTcl writes procedures in the interpreter that
belong to your application back into the main file. So if you generate a
VTcl file, then hand modify it to source your other file; if you load the
modified file back into VTcl and re-save it you will find the procedures
from your external file written into the VTcl generated file.
This is OK, but I like to keep some procedures in a separate file so they
are not accessed until they are needed.
Try NOT sourcing your file, but use the Tcl unknown procedure mechanism. So
generate a tclIndex file, then instead of sourcing the file, just call the
procedures by name. This has always worked for me.
Tony Chester
PS. Maybe Stewart can put a switch in VTcl to suppress the writing of user
procedures currently in the interpreter out to file?
British Telecommunications plc
Registered Office 81 Newgate Street London EC1A 7AJ
Registered in England no 1800000
