- Pharo-dev - lists.pharo.org

[update 3.0] #30349

by StÃ©phane Ducasse

30349 ----- - issue 11316 Add when:send:to: and deprecate on:do: Added more comments and when:do:for: as suggested by Henrik. https://pharo.fogbugz.com/default.asp?11316 - issue 11466 Speed up Refactoring-Tests-Core. Thanks Camillo Bruni. https://pharo.fogbugz.com/default.asp?11466 - issue 5331 MorphThreeModel>>#setPageSize: https://pharo.fogbugz.com/default.asp?5331 - issue 11469 2 small sorting fixes needed https://pharo.fogbugz.com/default.asp?11469 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Tests-Core-Stepha… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-Base-StephaneDucasse.… http://smalltalkhub.com/mc/Pharo/Pharo30/main/CollectionsTests-StephaneDuca… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Collections-Strings-StephaneD… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Collections-Sequenceable-Step… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Announcements-Core-StephaneDu…

Aug. 27, 2013

Re: [Pharo-dev] Debugger recursion

by Mariano Martinez Peck

If you take a look to Ghost proxies, in the proxy handler I have a dictionary in which users can define exceptions. That means, that the proxy handler will do something different than the expected action (like forwarding the message to another object). By default, I added some helper methods that add some of these exceptions. One of these, where a list of method to proper debug/inspect proxies. And the nice thing of being a dictionary is that you can enable/disable them even on the fly. Cheers, On Tue, Aug 27, 2013 at 5:09 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > > On 24 August 2013 14:18, jan.struz <public+pharo(a)struz.cz> wrote: > >> StÃ©phane Ducasse wrote >> > On Aug 23, 2013, at 7:13 PM, jan.struz < >> >> > public+pharo@ >> >> > > wrote: >> > >> >> Proxy implementation >> > >> > did you have a look at Ghost because mariano spent nearly a year on it. >> > >> > I do not really know what are the messages supposed to be supported by >> > ProtoObject to be debugged >> > May be it is not in the contract of ProtoObject and as such it produces >> > normally an infinite loop. >> > >> > Stef >> >> ok, so the rule is: never subclass ProtoObject to make Debugger crazy.. >> I will definitely look at Ghost, it has already been on my todo list.. >> >> i would say: > - if you subclass from ProtoObject then you are on your own.. don't expect > any standard tools to work anymore (including debugger, of course). > > And no, there is no 'fix' for that.. except from merging ProtoObject with > Object, > which kills the purpose of having ProtoObject class. > > thanks >> >> >> >> >> >> ----- >> Save The World! >> -- >> View this message in context: >> http://forum.world.st/Debugger-recursion-tp4704703p4704864.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> > > > -- > Best regards, > Igor Stasenko. > -- Mariano http://marianopeck.wordpress.com

Aug. 27, 2013

Re: [Pharo-dev] Debugger recursion

by Igor Stasenko

On 24 August 2013 14:18, jan.struz <public+pharo(a)struz.cz> wrote: > StÃ©phane Ducasse wrote > > On Aug 23, 2013, at 7:13 PM, jan.struz < > > > public+pharo@ > > > > wrote: > > > >> Proxy implementation > > > > did you have a look at Ghost because mariano spent nearly a year on it. > > > > I do not really know what are the messages supposed to be supported by > > ProtoObject to be debugged > > May be it is not in the contract of ProtoObject and as such it produces > > normally an infinite loop. > > > > Stef > > ok, so the rule is: never subclass ProtoObject to make Debugger crazy.. > I will definitely look at Ghost, it has already been on my todo list.. > > i would say: - if you subclass from ProtoObject then you are on your own.. don't expect any standard tools to work anymore (including debugger, of course). And no, there is no 'fix' for that.. except from merging ProtoObject with Object, which kills the purpose of having ProtoObject class. thanks > > > > > > ----- > Save The World! > -- > View this message in context: > http://forum.world.st/Debugger-recursion-tp4704703p4704864.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- Best regards, Igor Stasenko.

Aug. 27, 2013

fixing the Browser settings

by StÃ©phane Ducasse

Hi guys I need a good soul that can fix the opening of the setting browser. The TreeMorph got certainly touched and now it garbages a lot. Stef

Aug. 27, 2013

[update 3.0] #30348

by StÃ©phane Ducasse

Aug. 27, 2013

Re: [Pharo-dev] Compilation code in grease not compatible with Pharo 3.0

by Damien Cassou

thank you ClÃ©ment. That's what I came up with. Now, there is always the call to #putSource:fromParseNode:inFile:withPreamble: that is not implemented anymore: On Tue, Aug 27, 2013 at 7:53 PM, ClÃ©ment Bera <bera.clement(a)gmail.com>wrote: > putSource: aString > fromParseNode: methodNode > > inFile: 2 > withPreamble: > -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Aug. 27, 2013

Re: [Pharo-dev] Compilation code in grease not compatible with Pharo 3.0

by ClÃ©ment Bera

I didn't check (I'm not on my laptop) but I would say the problem is that CompiledMethodWithNode does not exist any more. Something like that would fix it: GRPharoPlatform>>compile: aString into: aClass classified: aSymbol "The trick here is to be as silently a possible so that the package is not marked dirty when running WAFileLibrary test. This also makes running tests much faster." | methodNode compiledMethod selector methodAndNode | methodNode := aClass compilerClass new source: aString; class: aClass; failBlock: [ GRError signal: 'syntax error' ]; translate. compiledMethod := methodNode generate: aClass defaultMethodTrailer. selector := methodNode selector. compiledMethod putSource: aString fromParseNode: methodNode inFile: 2 withPreamble: [ :file | aClass printCategoryChunk: aSymbol asString on: file priorMethod: (aClass compiledMethodAt: selector ifAbsent: [ nil ]). file cr ]. aClass addSelectorSilently: selector withMethod: compiledMethod. self doSilently: [ aClass organization classify: selector under: aSymbol ] 2013/8/27 Damien Cassou <damien.cassou(a)gmail.com> > Hi, > > how can I make the following code compile in Pharo 3.0? This is part of > Grease ( > https://ci.inria.fr/pharo-contribution/job/Grease/PHARO=30,VERSION=stable,V… > ): > > GRPharoPlatform>>compile: aString into: aClass classified: aSymbol > "The trick here is to be as silently a possible so that the package is > not marked dirty when running WAFileLibrary test. > This also makes running tests much faster." > | methodNode compiledMethod selector methodAndNode | > methodNode := aClass compilerClass new > compile: aString > in: aClass > notifying: nil > ifFail: [ GRError signal: 'syntax error' ]. > selector := methodNode selector. > methodAndNode := CompiledMethodWithNode > generateMethodFromNode: methodNode > trailer: aClass defaultMethodTrailer. > compiledMethod := methodAndNode method. > compiledMethod > putSource: aString > fromParseNode: methodAndNode node > inFile: 2 > withPreamble: [ :file | > aClass > printCategoryChunk: aSymbol asString > on: file priorMethod: (aClass compiledMethodAt: selector > ifAbsent: [ nil ]). > file cr ]. > aClass > addSelectorSilently: selector > withMethod: compiledMethod. > self doSilently: [ > aClass organization > classify: selector > under: aSymbol ] > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without losing > enthusiasm." > Winston Churchill >

Aug. 27, 2013

Re: [Pharo-dev] [update 2.0] #20619

by Sven Van Caekenberghe

On 24 Aug 2013, at 18:29, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Yes, super cool! Yeah, pure magic ! > On Sat, Aug 24, 2013 at 6:10 AM, MartinW <wm(a)fastmail.fm> wrote: > Goubier Thierry wrote > > Thanks Esteban :) > > > > The speedup on loading MC packages is 3x or more, so I though it is a > > crime not to make it available immediately, since there is no bug reports > > in all our tests and usages. > > Thanks Thierry for the backport! > > Yes, thank you both! While i haven't measured anything it feels MUCH faster > when i load extensive configurations. > > > > -- > View this message in context: http://forum.world.st/update-2-0-20619-tp4703465p4704839.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > > > > -- > Mariano > http://marianopeck.wordpress.com

Aug. 27, 2013

Re: [Pharo-dev] Debugger recursion

by jan.struz

I'm on Pharo 2, exactly this case - infinite loops or image crashes, I will try it in Pharo 3, and see the difference. ClÃ©ment Bera-4 wrote > Hello, > > Are you on Pharo 2 or 3 ? > > In Pharo 2, debugging or inspecting with ProtoObject subclasses resulted > in > infinite loops or image crashes. I tried to have a look with the new > debugger and inspectors in Pharo 3 but there is still some work to do. > > > 2013/8/24 jan.struz < > public+pharo@ > > > >> StÃ©phane Ducasse wrote >> > On Aug 23, 2013, at 7:13 PM, jan.struz < >> >> > public+pharo@ >> >> > > wrote: >> > >> >> Proxy implementation >> > >> > did you have a look at Ghost because mariano spent nearly a year on it. >> > >> > I do not really know what are the messages supposed to be supported by >> > ProtoObject to be debugged >> > May be it is not in the contract of ProtoObject and as such it produces >> > normally an infinite loop. >> > >> > Stef >> >> ok, so the rule is: never subclass ProtoObject to make Debugger crazy.. >> I will definitely look at Ghost, it has already been on my todo list.. >> >> thanks >> >> >> >> >> >> ----- >> Save The World! >> -- >> View this message in context: >> http://forum.world.st/Debugger-recursion-tp4704703p4704864.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> ----- Save The World! -- View this message in context: http://forum.world.st/Debugger-recursion-tp4704703p4705301.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 27, 2013

Compilation code in grease not compatible with Pharo 3.0

by Damien Cassou

Hi, how can I make the following code compile in Pharo 3.0? This is part of Grease ( https://ci.inria.fr/pharo-contribution/job/Grease/PHARO=30,VERSION=stable,V… ): GRPharoPlatform>>compile: aString into: aClass classified: aSymbol "The trick here is to be as silently a possible so that the package is not marked dirty when running WAFileLibrary test. This also makes running tests much faster." | methodNode compiledMethod selector methodAndNode | methodNode := aClass compilerClass new compile: aString in: aClass notifying: nil ifFail: [ GRError signal: 'syntax error' ]. selector := methodNode selector. methodAndNode := CompiledMethodWithNode generateMethodFromNode: methodNode trailer: aClass defaultMethodTrailer. compiledMethod := methodAndNode method. compiledMethod putSource: aString fromParseNode: methodAndNode node inFile: 2 withPreamble: [ :file | aClass printCategoryChunk: aSymbol asString on: file priorMethod: (aClass compiledMethodAt: selector ifAbsent: [ nil ]). file cr ]. aClass addSelectorSilently: selector withMethod: compiledMethod. self doSilently: [ aClass organization classify: selector under: aSymbol ] -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Aug. 27, 2013