For 2021 - online Python 3 training - see ((here)).
Our plans were to retire in summer 2020 and see the world, but Coronavirus has lead us into a lot of lockdown programming in Python 3 and PHP 7.
We can now offer tailored online training - small groups, real tutors - works really well for groups of 4 to 14 delegates. Anywhere in the world; course language English.
Please ask about private 'maintenance' training for Python 2, Tcl, Perl, PHP, Lua, etc.
Tcl packages, pkg_mkIndex, pkgIndex.tcl -what are they and why use them.
In the previous article [here]
, I wrote about namespaces and how - as our program grows - we need to keep named pieces of code and globally accessible variable in their own groups. And we do so using a structure that's very much like family names and forenames. As our program grows, we also need to separate out various sections of the code into different files, so they can be maintained by a different person, perhaps on a different maintainance cycle, and so that common code can be called into severl programs without it being duplicated.
So every language that we teach (there's a full list of our public courses here
) has some sort of capability to load code from multiple places into a single program. In Tcl, separate loading can be done on an adhoc basis via source
or more flexibly and formalised via package require
mechanism works as follows.
1. In the script file which contains the code for the package, use a package provide
- for example:
package provide table 1.0
2. Provide an index file in the folder in which the package is stored, called pkgIndex.tcl
. In this file will be a whole load of statements which define which packages are held in which file in the directory. You could
write it manually, but plese don't - there's a Tcl command called pkg_mkIndex
to do it for you - and you run it in a Tcl shell as follows:
pkg_mkIndex . *.tcl
3. In your program which requires the package, add the directory in which the package may by found to the variable called auto_path
lappend auto_path furniture
4. And (finally) package require
package require table
There are complete source files from yesterday's training on our site - [the package code]
and [a calling program]
. You'll note that the package file defines a namesapce. Although namespaces and packages are different facilities, its natural to use them together, with a package loading in a whole bundle of pieces of code neatly wrapped in a namespace. (written 2011-09-03)
Associated topics are indexed as below, or enter http://melksh.am/nnnn for individual articlesT213 - Tcl/Tk - Libraries, Packages and Namespaces 
example of Tcl namespaces and packages - (2004-12-10) 
Packages and Namespaces are like Suitcases and Aircraft - (2007-09-09) 
Tcl - learning how to use namespaces, packages and libraries together - (2008-02-02) 
Tcl - uplevel to run code at calling level - (2009-10-24) 
Separating groups of variables into namespaces - (2010-11-24) 
What is a namespace and why do we need them? - (2011-09-03) 
Loading packages in your Tcl program - (2015-10-09)
Some other Articles
Assigning values to variables within other statements - RubyRuby off the Rails?Making best use of the new enthusiasm for MelkshamData that we use during our training courses, and other training resourcesTcl packages, pkg_mkIndex, pkgIndex.tcl -what are they and why use them.Storing Tcl source code encoded, and running via your own C programUser defined sorting and other uses of callbacks in Tcl and TkPassing back multiple results in Tcl - upvar and uplevelIf its Sunday, must it be Weymouth?
4759 posts, page by page
Link to page ... 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96 at 50 posts per page
This is a page archived from The Horse's Mouth at
the diary and writings of Graham Ellis.
Every attempt was made to provide current information at the time the
page was written, but things do move forward in our business - new software
releases, price changes, new techniques. Please check back via
our main site for current courses,
prices, versions, etc - any mention of a price in "The Horse's Mouth"
cannot be taken as an offer to supply at that price.
Link to Ezine home page (for reading).
Link to Blogging home page (to add comments).