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 variable
> or some sort of config file for your script can
> help with that.
What if there is no tclsh.exe file at all? I thought
the point of stubs was to remove all the "junk" you
needed to know about a version of Tcl. Can we
just call Tcl_FindExecutable(NULL), will that
still set up the tcl library path properly?
> You can't really use "info nameofexecutable" to
> launch a script using tclsh, if you're running
> in a Java process through TclBlend.
We just want to be able to load Tcl and Tcl Blend
into a JVM without in the "proper" way. From everything
I have read on the newsgroup, Tcl_FindExecutable()
is the "one true way".
Mo DeJong
Red Hat Inc
----------------------------------------------------------------
The TclJava mailing list is sponsored by Scriptics Corporation.
To subscribe: send mail to [EMAIL PROTECTED]
with the word SUBSCRIBE as the subject.
To unsubscribe: send mail to [EMAIL PROTECTED]
with the word UNSUBSCRIBE as the subject.
To send to the list, send email to '[EMAIL PROTECTED]'.
An archive is available at http://www.mail-archive.com/tcljava@scriptics.com
