I'm posting this as a servoce to the community; if it's already well-know, I apologise for disturbing you all.
I like to develop my packages with a pgkIndex.tcl and then point TCLLIBPATH to them for testing. Once they are working, I install them as modules into lib/tcl9/site-tcl[1].
I'm posting this as a servoce to the community; if it's already
well-know, I apologise for disturbing you all.
I like to develop my packages with a pgkIndex.tcl and then point
TCLLIBPATH to them for testing. Once they are working, I install them as modules into lib/tcl9/site-tcl[1].
This technique runs into trouble, however, when I'm developing a new
version of a package that has an installed, module version. The problem
is that Tcl appears to find the module first so even if I have
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 57:48:44 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
4 files (9,632K bytes) |
| Messages: | 285,955 |