Robert
Well, I don't program in Java, so Jacl would be out. I have built
tclblend a few times over the years. But i never really had a real
need for it, so I didn't end up using it.
Too bad that tclblend doesn't end up in activetcl - particularly since
lately it seems that activetcl is shipping with threads enabled. that
would at least give it a higher distribution.
I would use tclblend if there were some sort of java class that I
needed for which I couldn't find a c or tcl extension counterpart.
I do use TclBlend in an LGPL application of mine, to enable writting
plugins in Java for that application (which also supports plugins in c,
c++, python & perl). I also wish this was in ActiveTcl, because it is
difficult to compile it, especially with stubs enabled :-)
I have never used Jacl though...
George
Sturgeon liver.
I'll be more explicit: both TclBlend and Jacl have their place.
What does "Interfacing with Java" mean to you? Whether to use
TclBlend or Jacl depends crucially on that answer.
With a gun held to my head, I'd conjecture that TclBlend is more
likely to match your situation.
JDBC, Hibernate, JMS.
http://www.patrickfinnegan.com/
Jacl is pretty easy to use, but only supports a (large) subset of the
things that TclBlend does.
Donal.
Do you mean would I use either of them, or which one would I use to
interface with Java? The answer the first question is "yes", and to the
second is "it depends".
TclBlend connects a JVM to a (C) Tcl process so that Tcl/C code can call
Java code and vice-versa. Jacl on the other hand is a port of the Tcl
interpreter to Java (lacking a few more recent features, but generally
good enough).
-- Neil