Abstracted from Tcl 9.0 WishList in order to make that page easier to read...
Better Support for static packages. Static packages should not need a pkgIndex.tcl somewhere on disc. And, instead of , perhaps a special command could be provided.
DKF - What's wrong with:
proc ::tcl::loadStatic {package} {
uplevel #0 [list load {} $package]
}That's not even backwards-incompatible!
Volker - I didn't know about that one. Nevertheless, what I wanted is some loading mechanism for systems that don't support the shlib stuff.
DKF - Well, we've done a lot to support shared libs better across platforms (load, stubs, packages, etc.) and there is always the mechanism outlined above for loading statically linked packages into a Tcl interpreter (provided they've registered themselves with Tcl_StaticPackage() of course.) What else could you possibly want?
Volker - A tcl that is easy to port to VxWorks, eCos, ThreadX and whatever else is around for embedded systems. In many cases you can count your blessings if your compiler supports ANSI-C syntactically. Anyway, the end result usually is a single executable that gets loaded in the on-chip-flash of your system. main() will be entered at switch on and left at switch off time. Forget everything about file systems, clock seconds or kinky things like modules, shlibs/dlls or other "newfangled desktop OS stuff". -)