Re: creating stand-alone extended tclsh
- From: wbp@xxxxxxxxxxxxxxxx (Will Parsons)
- Date: 30 Apr 2007 14:16:10 GMT
Larry W. Virden wrote:
On Apr 28, 8:26 pm, Will Parsons <oud...@xxxxxxxxxxxxxxxx> wrote:
I would like to create a tclsh with application-specific extensions.
Take a look at the Tk application and the mainline for the "wish"
application. That's a standardly distributed extension which
demonstrates this.
OK - I'll do that.
This approach was used quite a bit in the early days of Tcl. It isI want the extended tclsh to use in a test harness for application
also used by many who want tcl not as the heart of their application,
but as a relatively invisible part of their application.
What you will tend to see is more people talking about dynamically
loaded all the extensions, due to the ease it makes to distribute one
small interpreter and a few extensions. In the old days, people would
"slice and dice" tcl and extensions into various iterations, and that
got old fast :wink:.
I am uncertain what your goal is, but you might take a peek at what is
going on with the tclkit community. Tclkit is a tcl interpreter along
with a few statically linked extensions. The wiki (http://
wiki.tcl.tk/ ) as well as the starkit google forum, are some good
sources of info on that alternative.
software. As I mentioned to another responder, the static linkage is
due to the limitations of the platform I'm working on (QNX4).
- Will
.
- References:
- creating stand-alone extended tclsh
- From: Will Parsons
- Re: creating stand-alone extended tclsh
- From: Larry W. Virden
- creating stand-alone extended tclsh
- Prev by Date: Re: creating stand-alone extended tclsh
- Next by Date: Re: Packages and Expect
- Previous by thread: Re: creating stand-alone extended tclsh
- Next by thread: n00b saying "hi"
- Index(es):
Relevant Pages
|
