> > Nope, no "feature changes" are going into 1.2.6. I still have some
> > error message improvements that I want to add before 1.2.6
> > will go out but there are no features that need to be changed (IMHO).
> > A compiler switch for stubs might be a good thing to add to 1.3.
It might be easy, bu
> I thought the other problem with stubs was that one tclblend.dll
> could not be loaded into both a JDK 1.1 and a JDK 1.2 JVM.
The JDK issue is separate. The Tcl stubs mechanism only
helps you with the Tcl (and Tk) DLLs, not with the JDK
DLLs. We will still need to build separate versions for
Title: RE: [Tcl Java] Should Tcl Blend 1.2.6 use Tcl 8.2 or Tcl 8.3?
I'd agree with going to Tcl 8.3 for the binary releases now. The main people this might inconvenience are those who rely on the free parts of TclPro as an easy way to get Tcl/Tk/IncrTcl/Iwidgets/etc..., but since you can pic
On Tue, 4 Apr 2000, Scott Redman wrote:
I thought the other problem with stubs was that one tclblend.dll
could not be loaded into both a JDK 1.1 and a JDK 1.2 JVM.
> It's too bad that we can't make TclBlend stubs enabled,
> that would fix this. The problem with stubs is that
> the TclBlend DLL
It's too bad that we can't make TclBlend stubs enabled,
that would fix this. The problem with stubs is that
the TclBlend DLL can also be used as a shell, and shells
cannot use stubs (unless they located and load the
Tcl DLL). Since Jiang Wu seems to have fixed this feature
(using TclBlend as a s
