On Tue, 1 Jul 1997, Chris Kelly wrote:
> The reason I save in test mode is because I am changing procedures and
> testing repeatedly. vTcl doesn't seem to have control of the
> application in the way that a typical debugger does. As a result, if I
> create an endless loop in a tcl procedure or lock up in one of my
> c++/Fortran core routines vtcl will lock up as well and any changes are
> lost. Because the Fortran code I'm using is buggy I need to save a lot.
vtcl runs live in the same interpreter as the application and is thus
susceptible to the loaded application's bugs. it's effectively doing
introspection on a running app and trying to impose control through
widget bindings. This works reasonably well on the core tk widgets
but gets a little out of hand with things like Tix. it's also the reason
for enforcing init() and main() procedures.
> > 1.11 will change the way apps are stored during edit so this type of
> > situation cannot occur (i.e. typos in code, fonts, etc).
> >
> > -stewart-
>
> Will 1.11 do anything about this problem?
Yes. In 1.11 I'm moving to a project format where all widget information
is stored explicitly instead of using introspection. This will help
eliminate many of the frailties as well as making it easier to manage
the code at a source level instead of procedure level. This also helps
when putting vtcl projects into revision control systems or when you want
to bring external tcl code into an existing project.
-stewart-
