Here is the patch with the description of the problems solved in the patch.
Without the patch, my Java program causes an access violation when loading
TclBlend.
-- Jiang Wu
[EMAIL PROTECTED]
-Original Message-
From: Jiang Wu [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 04, 2000 3:
> Hmm, this patch wouldn't happen to fix the following odd error I'm currently
> chasing (below), would it?
>
> Exception in thread "main" java.lang.NullPointerException
> at tcl.lang.Interp.create(Native Method)
> at tcl.lang.Interp.(Interp.java:130)
> at scriptmanager.Sc
Wow, same day response, and no noise! (oops ;) Great email list.
> -Original Message-
> From: Mo DeJong [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 24, 2000 5:13 PM
> To: W. John Guineau
> Cc: Jiang Wu; [EMAIL PROTECTED]
> Subject: Re: [Tcl Java] RE: [Tcl Java] Tcl Blend vs JACL
>
>
There are a bunch of posts on this Jacl vs Tcl Blend
thread so I will try to respond to points from each.
W. John Guineau Wrote:
> We have a medium sized system (~250K lines of C++ and Java) that
> we want to graft Tcl scripting into.
>
> The place where we would integrate scripting is all Jav
On Wed, 24 May 2000, Bruce Johnson wrote:
> Any hope that there will ever be a byte-code compiler for Jacl?
>
> Bruce
I am sure someone could port the C version of the Tcl Bytecode
compiler over to Jacl, but I was not planning on working it :)
There are a couple of ways one could do Byte compi
Jeff, sounds like your experience confirms my initial analysis - It's a safe
bet to go the Java -> Tcl Blend direction.
BTW - this work is for JPL (Jet Propulsion Laboratory) - so you can add JPL
to the list of "large corporate/gov't users of Tcl and Tcl Blend ;) We will
be using Tcl to script ou
Ah, thank you for the document pointer! This looks to be the motherload of
Tcl Blend/JACL info!
john
> -Original Message-
> From: Jiang Wu [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 24, 2000 2:24 PM
> To: 'W. John Guineau'; [EMAIL PROTECTED]
> Subject: RE: [Tcl Java] Tcl Blend vs
Any hope that there will ever be a byte-code compiler for Jacl?
Bruce
The TclJava mailing list is sponsored by Scriptics Corporation.
To subscribe:send mail to [EMAIL PROTECTED]
with the word SUBSCRIBE as the
"W. John Guineau" wrote:
> Well, if I use the Java package, then the Tcl code would not have access to
> the same run-time instance of the JVM that our code is running in, right?
I don't see why not. There is only one JVM per process anyway. (That
is a limitation of the Sun JVM.) I'm not famil
Well, if I use the Java package, then the Tcl code would not have access to
the same run-time instance of the JVM that our code is running in, right?
(starting our Java code from Tcl is, unfortunetly, not an option.) Or am I
missing something here?
My assumption was that starting a Tcl interpret
"W. John Guineau" wrote:
> My plan is to load the Tcl interpreter from within Java,
> and then interact with it from Java. We would then write
> Tcl extensions that essentially wind thier way back into
> our Java code, and therefore have access to all the
> functionality we already have. We wi
You are certainly "going against the grain" right now :) But I am hoping
more people will use TclBlend this way.
We are doing something similar right now with TclBlend (1.3 + some patches)
with JDK 1.2. I am not sure what you mean by "single step the interpreter".
You can certainly set/get/call
We have a medium sized system (~250K lines of C++ and Java) that we want to
graft Tcl scripting into.
The place where we would integrate scripting is all Java code.
I see the recommended solution in this case is to use JACL, but for
performance reasons (and other factors) I would prefer to use
Mo DeJong wrote:
> Thanks for the bug report and patch. Your suggested
> change was committed to the CVS with one small
> modification. If you have any other problems running
> Jacl in applets please don't hesitate to report them.
Thanks Mo. Actually I am not running applets, but the same applie
On Tue, 23 May 2000, Jeff Sturm wrote:
> I just tracked down an annoying bug in Jacl... the classloader could not
> found a /tcl/lang/library/init.tcl resource, so the interpreter refused
> to start.
>
> The Interp had been trying to load resources from the system
> classloader, not the classloa
15 matches
Mail list logo
