> This is in fact only partially true. You can't just extend an > existing > module, like adding another method to class XYZ. You will have to > rewrite the whole library containing the class instead. And that's > exactly what happens: The teams are rewriting the kits. You can actually. It just involves some fiddling with the linker to duplicate exported symbols. I've done it before, in fact. > But your statement is also not completely true in another respect: > The > mammoth part of the API lives in one library, in libbe.so. So if you > want to modify a tiny function in the app, interface, support or > storage kit (do I miss one?), you will need to reimplement the whole > beast. And not only the library, but also app server and registrar. > > So actually we are exactly doing what also had to be done when > following the approach you propose. And by staying focussed on the > reimplemention, rather than also extending/improving things, we will > much faster reach our goal of a self-contained OS. An OS that can > legally be distributed, as opposed to a modified R5 PE. You could, of course, distribute a patch to PE. -Nathan -- Fortune Cookie Says: Those of you who think you know everything are very annoying to those of us who do.