Ticket #0002126

Summary	Internal modules
Description	We have been planning to make it possible to split the built-in functions and words into groups, and then make some of those groups optional. This is part of why we added modules in the first place. The backwards compatibility policies depend on this too, since we want the old-style functions to be not loaded unless people need them. However, due to the bootstrapping process we're going to need two kinds of modules. After the mezzanines and such are loaded you can use regular modules, since the infrastructure for them is there. For modules made during the bootstrap process though, such as those which contain natives, we need to fake them. Fortunately we can do this with available natives and actions, we don't have to make anything new. The native bootstrap generator will need namespace support. There will need to be a minimal boot time MODULE function which calls TO instead of MAKE, passed an object instead of a body, which gets overridden with the regular MODULE afterwards. Embedded extensions will still need their special loader, after the mezzanines start. Most of those will depend on the runtime library functions anyways. We don't at this point even need to choose what we want to or can put into which modules, this is just the making-it-possible step.
Example code

Assigned to	n/a	Fixed in	-	Last Update	6-Mar-2014 07:51