Home All Groups Group Topic Archive Search About
Author
7 Mar 2009 12:56 PM
IJALAB
Hello all,

We have a tool developed in Visual Basic 6.0. The scripting
functionality is implemented as follows.
The tool's user interface functions are mapped to a script command and
user can write script commands and run on the tool. The script
commands in a text file will be stored on to memory and then executed
on a line by line basis by the tool.the limitation is we are unable to
perform any dynamic checks on the script. like dynamic updation to the
script or stopping the script based on some variable value etc.
because the script commands are executed from memory. can someone give
guidelines so that we want to get rid of these gating factors in teh
script engine?

Author
7 Mar 2009 2:03 PM
Larry Serflaten
"IJALAB" <balaji.d***@gmail.com> wrote

> We have a tool developed in Visual Basic 6.0. <....>
> The script commands in a text file will be stored on to memory
> and then executed on a line by line basis by the tool.

> the limitation is we are unable to perform any dynamic checks
> on the script.

It would seem, at first glance, that you need to provide a hook
after the execution of each line.  You would need to provide
a means to allow checks for environment conditions after each
and every line of script.

But, how does the tool know what to check for, unless that
also is in another set of script commands?

It would seem you need to add a little more design work to
the tool....

LFS