Using packages and namespaces together

Libraries, Packages and Namespaces example from a Well House Consultants training course
More on Libraries, Packages and Namespaces [link]

This example is described in the following article(s):
• Tcl - learning how to use namespaces, packages and libraries together - [link]

Source code: dinpack Module: T213

lappend auto_path /Users/grahamellis/jtc/stuffing

set comment {
This is an example script that calls in two packages
called chicken and goose from a library. Each of the
two packages is in the same namespace as the name of
the package (to make it easier to understand and
maintain) event though - technically speaking - the
package and namespace facilities are not related. }

package require chicken
package require goose

# The following line mean that any names that were
# made available from the goose namespace may be used
# here without a goose:: prefix.

namespace import goose::*

set people 12

# Run the sizebird command in each of chicken and goose
# because we have different namespaces, we can have two
# commands with the same name.

set kilos [chicken::sizebird $people]
puts "You need a ${kilos}kgs bird if it's a chicken"

set kilos [goose::sizebird $people]
puts "You need a ${kilos}kgs bird if it's a goose"

# and run the "default" one - i.e. the one in the global
# namespace; this is the goose one because of the import

set kilos [sizebird $people]
puts "You need a ${kilos}kgs bird if it's imported"

Learn about this subject

This module and example are covered on the following public courses:
* Learning to program in Tcl
* Tcl Programming
* Tcl Programming
Also available on on site courses for larger groups

Books covering this topic

Yes. We have over 700 books in our library. Books covering Tcl, Tk and Expect are listed here and when you've selected a relevant book we'll link you on to Amazon to order.

Other Examples

This example comes from our "Libraries, Packages and Namespaces" training module. You'll find a description of the topic and some other closely related examples on the "Libraries, Packages and Namespaces" module index page.

Full description of the source code

You can learn more about this example on the training courses listed on this page, on which you'll be given a full set of training notes.

Many other training modules are available for download (for limited use) from our download centre under an Open Training Notes License.

Other resources

• Our Solutions centre provides a number of longer technical articles.
• Our Opentalk forum archive provides a question and answer centre.
• The Horse's mouth provides a daily tip or thought.
• Further resources are available via the resources centre.
• All of these resources can be searched through through our search engine
• And there's a global index here.

Web site author

This web site is written and maintained by Well House Consultants.

Purpose of this website

This is a sample program, class demonstration or answer from a training course. It's main purpose is to provide an after-course service to customers who have attended our public private or on site courses, but the examples are made generally available under conditions described below.

Conditions of use

Past attendees on our training courses are welcome to use individual examples in the course of their programming, but must check the examples they use to ensure that they are suitable for their job. Remember that some of our examples show you how not to do things - check in your notes. Well House Consultants take no responsibility for the suitability of these example programs to customer's needs.

This program is copyright Well House Consultants Ltd. You are forbidden from using it for running your own training courses without our prior written permission. See our page on courseware provision for more details.

Any of our images within this code may NOT be reused on a public URL without our prior permission. For Bona Fide personal use, we will often grant you permission provided that you provide a link back. Commercial use on a website will incur a license fee for each image used - details on request.