> -Original Message-
> > Sorry, I haven't been following this thread.
> >
> > You can't have any idea where the tclsh.exe lives,
> > unless it's in you're PATH or (on Windows) in the
> > registry. You can't even know the name (is it
> > tclsh.exe or tclsh83.exe?), maybe a global variab
On Fri, 30 Jun 2000, Scott Redman wrote:
> Sorry, I haven't been following this thread.
>
> You can't have any idea where the tclsh.exe lives,
> unless it's in you're PATH or (on Windows) in the
> registry. You can't even know the name (is it
> tclsh.exe or tclsh83.exe?), maybe a global variabl
> -Original Message-
> From: Mo DeJong [mailto:[EMAIL PROTECTED]]
>
> Please provide an example where the internal rep get hosed inbetween
> the call to java::new and the call to set. This should never happen.
Like I said, it "may or may not" work. So use at your own risk. Here is
the
Sorry, I haven't been following this thread.
You can't have any idea where the tclsh.exe lives,
unless it's in you're PATH or (on Windows) in the
registry. You can't even know the name (is it
tclsh.exe or tclsh83.exe?), maybe a global variable
or some sort of config file for your script can
help
