[GOODIE] Unloadable definitions management (Was: Re: Optional class
extensions)
Cees de Groot
cg at cdegroot.com
Sat Feb 5 22:32:29 UTC 2005
On Sat, 5 Feb 2005 17:36:58 +0100, Bert Freudenberg <bert at impara.de> wrote:
> But why would you need to use a different category then? Just make a
> preference to ignore any definitions with unmet requirements when
> loading and you're set, no?
>
Or better, handle unloadable definitions like VW - keep them around, make
them browseable, and check whether any of them now load after a fileIn.
More or less what the attached code does - it's probably rough and
incomplete, but it should allow you to load changesets in any ol'd random
order.
The attached package overrides PositionableFileStream>>fileIn:
The attached package is ALPHA quality code
-> You've been warned, haven't you? ;)
Unloadable definitions are kept in UnloadableClass objects in the
Unloadable global. At the end of a fileIn, these definitions are checked,
and if any classes that are in Unloadable have appeared in the image,
these classes are loaded and removed from Unloadable. If Unloadable ain't
empty after a fileIn, an inspector is popped up on it (should become a
browser, and there is more to clean up, but this should show what this is
aiming at).
Using this package should make it easy to work on dependencies etcetera
for packages - load any package in a very small image, and check
Unloadable for what's missing.
Have fun,
Cees
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Tric-Unloadable-CdG.1.mcz
Type: application/octet-stream
Size: 4597 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20050205/1ecba25e/Tric-Unloadable-CdG.1.obj
More information about the Squeak-dev
mailing list
|