Re: [Pharo-project] problem with obsolete classes in latest core
On Mar 25, 2011, at 3:46 PM, Marcus Denker wrote:
fixObsoleteReferences only fixes CompiledMethods, doesn't it ?
yep.
And the trick to find them is to inspect SystemNavigation default obsoleteClasses first allInstances and then use the "explore pointers" on that. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
On Mar 25, 2011, at 3:48 33PM, Marcus Denker wrote:
On Mar 25, 2011, at 3:46 PM, Marcus Denker wrote:
fixObsoleteReferences only fixes CompiledMethods, doesn't it ?
yep.
And the trick to find them is to inspect
SystemNavigation default obsoleteClasses first allInstances
and then use the "explore pointers" on that.
Marcus
Soooo... WordArrayForSegment in System-Object Storage is now a subclass of AnObsoleteWordArray? What on earth did that update try to do? ;) Cheers, Henry
On Mar 25, 2011, at 4:09 51PM, Henrik Johansen wrote:
On Mar 25, 2011, at 3:48 33PM, Marcus Denker wrote:
On Mar 25, 2011, at 3:46 PM, Marcus Denker wrote:
fixObsoleteReferences only fixes CompiledMethods, doesn't it ?
yep.
And the trick to find them is to inspect
SystemNavigation default obsoleteClasses first allInstances
and then use the "explore pointers" on that.
Marcus
Soooo... WordArrayForSegment in System-Object Storage is now a subclass of AnObsoleteWordArray?
What on earth did that update try to do? ;)
Cheers, Henry
Oh, move it from one category to another. Figures that's so complicated an operation it would break all subclasses etc. Cheers, Henry
On Mar 25, 2011, at 4:12 02PM, Henrik Johansen wrote:
On Mar 25, 2011, at 4:09 51PM, Henrik Johansen wrote:
On Mar 25, 2011, at 3:48 33PM, Marcus Denker wrote:
On Mar 25, 2011, at 3:46 PM, Marcus Denker wrote:
fixObsoleteReferences only fixes CompiledMethods, doesn't it ?
yep.
And the trick to find them is to inspect
SystemNavigation default obsoleteClasses first allInstances
and then use the "explore pointers" on that.
Marcus
Soooo... WordArrayForSegment in System-Object Storage is now a subclass of AnObsoleteWordArray?
What on earth did that update try to do? ;)
Cheers, Henry
Oh, move it from one category to another.
Figures that's so complicated an operation it would break all subclasses etc.
Cheers, Henry
Why move them to begin with btw? Are they not arrayed? Isn't ByteArray "native" too, following whatever rationale was followed when moving Word/Float/IntegerArrays there? How about the rest of the variable Word/Byte subclasses? This way just looks silly, imho... Cheers, Henry
participants (2)
-
Henrik Johansen -
Marcus Denker