As a "repeater offender" you will probably don't answer be. But anyway... we were discussing a couple of days ago with the Pharo guys about unloading and the biggest problem we found were the overrides of the packages. Do you handle this situation? <br>
<br>Thanks<br><br>Mariano<br><br><div class="gmail_quote">On Sun, Jan 3, 2010 at 3:09 PM, Andreas Raab <span dir="ltr"><<a href="mailto:andreas.raab@gmx.de">andreas.raab@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Folks -<br>
<br>
I've been going through various packages, and we're actually capable of unloading quite a bit of them cleanly by now. I've attached my unload script which (on a most recent updated trunk image with no additional packages loaded) will be able to unload the following packages:<br>
- ReleaseBuilder, ScriptLoader<br>
- 311Deprecated, 39Deprecated<br>
- Universes, SMLoader, SMBase, Installer-Core<br>
- VersionNumberTests, VersionNumber<br>
- Services-Base, PreferenceBrowser, Nebraska<br>
- CollectionsTests, GraphicsTests, KernelTests, MorphicTests<br>
- MultilingualTests, NetworkTests, ToolsTests, TraitsTests<br>
- XML-Parser, Traits<br>
After these packages been unloaded there are no Undeclared references or obsolete behaviors or modified MC packages. There are several more candidate packages, some of which I could use some help with:<br>
<br>
* Tests: The tests package is currently not unloadable because it includes ClassTestCase which is used from several other places. There is a fundamental question here whether we should aim for making all tests as well as SUnit unloadable or not. If the former, then we need to move tests out of packages like Files, System or MC in order to make them unloadable. If we're not shooting for making SUnit unloadable it may be worthwhile to promote ClassTestCase up to SUnit so that the Tests package becomes unloadable. Comments?<br>
<br>
* Morphic-Extras: I don't understand the intent of this package. The name implies to me that it includes "extras" which I'd expect to be optional content that should be unloadable at will but the reality is that even attempting to unload it (I foolishly tried) blows up left and right. Question: Is the intention of Morphic-Extras to contain unloadable content? If so, it's not doing its job currently. If that's not the intention of Morphic-Extras, I'd appreciate a heads-up of what the rationale for the structure is.<br>
<br>
* ST80: This is still a bit off but we're getting there. It can actually be unloaded but there are still several Undeclared variables and obsolete behaviors after unloading MVC. But the good news is that the system is still functioning (!) instead of horribly dying as it used to be. We could use a bit of additional help from people with an interest in this area.<br>
<br>
Cheers,<br><font color="#888888">
- Andreas<br>
</font><br><br>
<br></blockquote></div><br>