March 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] problem with obsolete classes in latest core

by Henrik Johansen

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

March 25, 2011

Re: [Pharo-project] Issue 3877 in pharo: Check reduced complexity for UI themes

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #1 on issue 3877 by marcus.d...(a)gmail.com: Check reduced complexity for UI themes http://code.google.com/p/pharo/issues/detail?id=3877 (No comment was entered for this change.)

March 25, 2011

Re: [Pharo-project] Issue 3878 in pharo: #enableTextChange selector name is misleading, i propose changing the name to #canChangeText

by pharo＠googlecode.com

Updates: Status: FixProposed Labels: Milestone-1.3 Comment #1 on issue 3878 by marcus.d...(a)gmail.com: #enableTextChange selector name is misleading, i propose changing the name to #canChangeText http://code.google.com/p/pharo/issues/detail?id=3878 (No comment was entered for this change.)

March 25, 2011

Re: [Pharo-project] problem with obsolete classes in latest core

by Henrik Johansen

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

March 25, 2011

Re: [Pharo-project] problem with obsolete classes in latest core

by Henrik Johansen

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

March 25, 2011

[Pharo-project] Issue 3881 in pharo: Problem with Inst var refs...

by pharo＠googlecode.com

Status: FixProposed Owner: Benjamin...(a)gmail.com Labels: Nautilus New issue 3881 by Benjamin...(a)gmail.com: Problem with Inst var refs... http://code.google.com/p/pharo/issues/detail?id=3881 If you click, the popup window have the good name, but if you choose to sort var names alphabetically, you have a stupid name Attachments: FixTitleIssueInInstVarBrowser.1.cs 748 bytes

March 25, 2011

Re: [Pharo-project] problem with obsolete classes in latest core

by Marcus Denker

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.

March 25, 2011

Re: [Pharo-project] problem with obsolete classes in latest core

by Marcus Denker

On Mar 25, 2011, at 3:44 PM, Mariano Martinez Peck wrote: > > > On Fri, Mar 25, 2011 at 3:41 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Mar 24, 2011, at 7:25 PM, Mariano Martinez Peck wrote: >> Compiler recompileAll. >> Smalltalk fixObsoleteReferences. >> >> SystemNavigation default obsoleteClasses ->>> an Array(AnObsoleteWordArray) >> >> But I cannot get rid of that final obsoletClass. >> > > > If you check for the users of WordArray, they are stored in some class vars... > > BalloonEngine initialize. > DataStream initialize. > DeflateStream initialize. > FastInflateStream initialize. > ZipConstants initialize. > ZipWriteStream initialize. > PNGReadWriter initialize > > seems to solve it. > > Thanks Marcus...so...I am trying to understand the problem. You are saying that if there is a class stored in an instVar somewhere, class var. > and I remove/renamed or whatever that class, then those instVar will be pointing to the obsolete one? yes. > fixObsoleteReferences only fixes CompiledMethods, doesn't it ? > yep. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 25, 2011

Re: [Pharo-project] Issue 3681 in pharo: [Failing Test] Tests.Release.ReleaseTest.testObsoleteClasses

by pharo＠googlecode.com

Updates: Status: FixProposed Labels: Milestone-1.3 Comment #5 on issue 3681 by marcus.d...(a)gmail.com: [Failing Test] Tests.Release.ReleaseTest.testObsoleteClasses http://code.google.com/p/pharo/issues/detail?id=3681 for 1.3 in addtion: WordArrayForSegment has Obsolete super. fix that and evaluate in the postscript: BalloonEngine initialize. DataStream initialize. DeflateStream initialize. FastInflateStream initialize. ZipConstants initialize. ZipWriteStream initialize. PNGReadWriter initialize

March 25, 2011

Re: [Pharo-project] problem with obsolete classes in latest core

by Mariano Martinez Peck

On Fri, Mar 25, 2011 at 3:41 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Mar 24, 2011, at 7:25 PM, Mariano Martinez Peck wrote: > > Compiler recompileAll. > Smalltalk fixObsoleteReferences. > > SystemNavigation default obsoleteClasses ->>> an > Array(AnObsoleteWordArray) > > But I cannot get rid of that final obsoletClass. > > > If you check for the users of WordArray, they are stored in some class > vars... > > BalloonEngine initialize. > DataStream initialize. > DeflateStream initialize. > FastInflateStream initialize. > ZipConstants initialize. > ZipWriteStream initialize. > PNGReadWriter initialize > > seems to solve it. > Thanks Marcus...so...I am trying to understand the problem. You are saying that if there is a class stored in an instVar somewhere, and I remove/renamed or whatever that class, then those instVar will be pointing to the obsolete one? fixObsoleteReferences only fixes CompiledMethods, doesn't it ? cheers Mariano > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

March 25, 2011