On Wed, Jun 4, 2008 at 9:41 AM, Klaus D. Witzel <[EMAIL PROTECTED]> wrote:
> What you want to see (according to your question about object removal) is > just the empty array; and what I wanted to point out (without hair-splitting > ;) is, that when you GC+check this within the same method, it *must* fail. I guess it would have to, wouldn't it? In Smalltalk it's very easy to script the removal+GC+check, for example in a > workspace or add GC+check temporarily in a debugger session; that was my > concern. > A good example for maintaining parent/child objects, which works perfectly, > is Smalltalk's #addSubclass: #removeSubclass: (both on the instance side of > Class); when you check these two methods think that 'superclass' is your > parent pointer. Thanks for pointing this out--maybe I can learn something and get this working properly! Rob
_______________________________________________ Beginners mailing list Beginners@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/beginners
