Re: tcltest Tk Applications

"Erik Leunissen" <look@xxxxxxxxxxxxxxxxxx> wrote
>
> > I just found a fix for the problem that I addressed in the
previous
> > posting. See the code inside "setupScript" in the test script
below.
> >
>
> But all access to files other than stdout, stderr and stdin will
remain
> a very big ... PITA


Thanks, Erik, for the caution and workaround on standard channels and
slave interps. That's one issue I hadn't considered, but could be
included in the strategy.

But I don't see that as a serious problem for many file I/O tests.
The example you provide (proc writeToFile) could be handled with
regular tcltests, without the use of slave interps. My proposed use
of slave interps was to facilitate full Tk applications. Stdin/stdout
could be a significant issue. But most file I/O shouldn't be a
problem, because all the code will be run by the slave. (It won't
have to straddle interpreters.)

Bob
--
Bob Techentin techentin.robert@xxxxxxxxxxxxxx
Mayo Foundation (507) 538-5495
200 First St. SW FAX (507) 284-9171
Rochester MN, 55901 USA http://www.mayo.edu/sppdg/



.