......
> > - after Tcl, Tk, trf, memchan, vfs built, they could be linked with
> > Tcl.xs we get single Tcl.dll, (otherwise Perl's Tcl.dll calls
> > Tcl/Tk's tcl84.dll and tk84.dll)
> > - "tcl-scripts.zip" created during build
> > - all related *.tcl scripts being used from
> "tcl-scripts.zip" archive
> > directly using Tcl's vfs::zip vrtual FS.
>
> This is interesting. We (ActiveState) have done something
> similar for our own purposes. We did this by basing the
I did not finalized my initial idea at previous weekend, unfortunately, as I
was stuck in helping friends with their hardware problems.
However I am planning to finalize it really soon.
I will name modules as Tcl-packaged and Tcl-zpackaged, if no better name
will be suggested ot come into my mind.
It would be highly beneficial for fully feature-enabled module to be placed
in 4-5 library files and zip-archived file with scripts...
> work on starpacks as dlls. You will see some of the code
> that I commited to Tcl.xs to support this.
That's very good, and few questions though.
Your code mostly refers to __hpux, which I am not familiar.
Did I understood correctly that "sl" in "libtcl8.4.sl" stands for "starpack
library"?
Why only __hpux then, why not any linux system also involved?
Best regards,
Vadim.
|