The 1.2 "stable" version of Tcl Blend was tested with Tcl 8.0, Tcl 8.1,
and Tcl 8.2. It should also work with Tcl 8.3 but more testing is needed.
The 1.3 "development" version of Tcl Blend will only work with Tcl 8.3
and newer versions of Tcl.
The 1.2 version of Tcl Blend is frozen, no new featu
Is TclBlend 1.2.x supposed to also work with Tcl 8.0? There are seem to be
some stuff in the source code that tries to make TclBlend compatible with
Tcl 8.0. If I want to make a patch to TclBlend 1.2.x, do I need to worry
about Tcl 8.0? For example, I'd like to add support to do
"Interp.evalFil
Ok, I will put a "package require Tcl 8.3" check into the configure.in
and pkgIndex.tcl files so that Tcl Blend 1.3 will only work on Tcl 8.3
and newer systems.
If anyone wants to run Tcl Blend on older 8.0 -> 8.2 versions of Tcl
they can use the stable release.
Mo Dejong
Red Hat Inc.
On Thu, 2
Tcl 8.2.3 uses "vfork" instead of "fork". Apparently, "vfork" produces a
child process that shares the parent process's signal handlers. Then the
Tcl code calls "RestoreSignals()" in the child process to make the signal
handlers back to defaults. But this also changed the parent process's
signa
Try hammering in "fork" instead of "vfork".
Look also at the signal code in Tcl itself - it may be resetting
some signals
>>>Mo DeJong said:
> I just ran your example and got a core dump with Tcl Blend 1.2.5
> and JDK-1.2.1_03 on a Solaris 5.6 box. This is a mighty strange
> one. Why would the
