Brief intro to Modules and DeltaModules
Last updated at 4:40 pm UTC on 16 January 2006
Modules can be viewed as standalone collections of global variable definitions (classes etc.). They live in a namespace of their own and if they reference other classes in other modules, those modules become so called "external modules" to the module. It's more or less like an "import" I guess. So a module "depends" on other modules in this way.
(See How to declare module dependencies.)
So far so good - it is quite logical that a module has a namespace of its own, it also seems quite logical that it needs to, in order to be a real module - otherwise it would be able to clash with other classes having the same names in other modules. Now it only needs to make sure that the "external modules" don't have clashing classes (globals).
The ideas that a module only contains standalone classes (and no loose class extensions, see below) they are by definition loadable without conflict. It's just a bunch of classes that can't possible affect anything.
Ok, here comes the tricky - but I would also like to say - the neat thing: a DeltaModule.
Read on on Brief intro to Modules and DeltaModules
– Göran Hultgren
