Squeak
  links to this page:    
View this PageEdit this PageUploads to this PageHistory of this PageTop of the SwikiRecent ChangesSearch the SwikiHelp Guide
Hans-Martin on Packages and Namespaces
Last updated at 12:39 pm UTC on 27 February 2005
IMO, the concepts of packages (separately loadable pieces of code) and namespaces (registries of named code artefacts) should be kept separate.
Both are valuable, and neither fulfills the other's role.

Packages

Namespaces


Of course, typical "applications" can have a package and a namespace going together, with the package author being the naming authority of the namespace. However, even for moderately complex systems I can envision several packages which are independently versioned but which define their artefacts within just one namespace.

Hans-Martin Mosner
Note: This has previously be called "Modules vs. Namespaces". After some reading, I realized that modules is a too general notion and that the different approaches to modularization of systems just cut along different planes. So it is probably valid to call all of these approaches "modularization mechanisms"