October 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] haltOnce and haltOnCount
by Marcus Denker Oct. 1, 2010

Oct. 1, 2010

On Oct 1, 2010, at 8:08 PM, Hernan Wilkinson wrote: > > PS: A #haltIf: aBlock message would be handy too :-) already there: 1 haltIf: [1<2]. 1 haltIf: [:rec | rec isInteger]. 1 haltIf: (1<2). 1 haltIf: #doIt especially putting a symbol is very useful. e.g. you can out the selector of the test and then even put a haltIf: into system methods called all the time. (e.g. collections). Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

Re: [Pharo-project] haltOnce and haltOnCount
by StÃ©phane Ducasse Oct. 1, 2010

Oct. 1, 2010

+ 1 really really important On Sep 30, 2010, at 11:38 PM, Alexandre Bergel wrote: > I used haltOnce quite often when I had to debug the rendering facilities in Mondrian. > Putting "self halt" in a drawOn: method can easily freeze your image. > > Alexandre > > > > On 30 Sep 2010, at 17:18, Hernan Wilkinson wrote: > >> Hi, >> when are these messages used? what are the scenarios? >> I just want to understand why they are there... >> >> -- >> HernÃ¡n Wilkinson >> Agile Software Development, Teaching & Coaching >> Mobile: +54 - 911 - 4470 - 7207 >> email: hernan.wilkinson(a)10Pines.com >> site: http://www.10Pines.com >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

3 2

[Pharo-project] Another fixes to finalization (was Re: [update 1.2] #12161 - #12172)
by Igor Stasenko Oct. 1, 2010

Oct. 1, 2010

I uploaded new changesets to http://code.google.com/p/pharo/issues/detail?id=3002 I tested applying them in Pharo-Core-#12159 and then updating an image after that. After update: MCMethodDefinition cachedDefinitions size is 18668 But image don't feels slow. As a side note, i recommend to review the MC caching mechanism towards avoiding putting so much load on finalization process (such as scanning 18k entries to find dead objects). This is actually the purpose of new finalization scheme: - it allows to avoid scanning whole weak dictionary in order to get rid of expired associations. I'm already implemented a variant of self-cleaning weak dictionary for Magma, which using new finalization scheme, and avoids scanning huge number of entries to discover few of them, which became garbage. -- Best regards, Igor Stasenko AKA sig.

2 4

Re: [Pharo-project] [squeak-dev] Re: Help is now able to define where subbooks are placed
by Hannes Hirzel Oct. 1, 2010

Oct. 1, 2010

Yes, this is very useful for me. Thank you Enrico and Thorsten! --Hannes On 10/1/10, Enrico Spinielli <enrico.spinielli(a)googlemail.com> wrote: > Torsten, > all thanks go to you for having thought/designed/implemented _and_ for > following HelpSystem up! > > Well done > Bye > Enrico > > On Fri, Oct 1, 2010 at 00:19, Torsten Bergmann <astares(a)gmx.de> wrote: >> Hi Enrico, >> >> found the time this evening to integrate your idea >> that custom help books should be able to define >> where subbooks should be placed/displayed: >> >> Â Â #pages >> Â Â Â ^(firstPage MyAppSubTutorial secondPage thirdPage) >> >> >> Just update your Squeak image to #10565 and you dont >> need to workaround this problem using a custom >> builder anymore. >> >> It is now also mentioned in the help systems help >> itself. See chapter "STEP 7 - TIPS AND TRICKS". >> >> I've also opened an issue together with the >> changeset for Pharo 1.2 so that it will be >> integrated in one of the next pharo updates. >> >> http://code.google.com/p/pharo/issues/detail?id=3022 >> >> Thanks for the idea and initial code! >> >> Bye >> T. >> -- >> Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! >> Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail >> > > > > -- > Enrico Spinielli > "Do Androids dream of electric sheep?"â Philip K. Dick > "Hear and forget; see and remember;do and understand."âMitchel Resnick > >

1 0

[Pharo-project] Base64MimeConverterTest>>#testOnByteArray raise an error
by Cyrille Delaunay Oct. 1, 2010

Oct. 1, 2010

ByteArray >> base64Encoded is no longer defined in Pharo 1.2, but used in the test Base64MimeConverterTest>>#testOnByteArray. It raise a DNU message. I opened an Issue: http://code.google.com/p/pharo/issues/detail?id=3027&q=base64Encoded&colspe…

2 1

[Pharo-project] Issue 3047: REFACTOR: Added intention revealing helper method to AppRegistry class>>register:
by Sean P. DeNigris Oct. 1, 2010

Oct. 1, 2010

http://code.google.com/p/pharo/issues/detail?id=3047 Old: register: aProviderClass ... default := nil. "so it'll ask for a new default..." ... New: ... self askForNewDefaultOnNextRequest. ... Fix in inbox: System-Applications-SeanDeNigris.15 -- View this message in context: http://forum.world.st/Issue-3047-REFACTOR-Added-intention-revealing-helper-… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 0

[Pharo-project] Issue 3046: BUG: LineMorph class>>from:to:color:width: returns a PolygonMorph
by Sean P. DeNigris Oct. 1, 2010

Oct. 1, 2010

http://code.google.com/p/pharo/issues/detail?id=3046 Fix in inbox: Morphic-SeanDeNigris.625 LineMorph class>>from:to:color:width: changed to return a LineMorph Sean -- View this message in context: http://forum.world.st/Issue-3046-BUG-LineMorph-class-from-to-color-width-re… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 0

[Pharo-project] Issue 3045: DOCUMENTATION: Added comment to RBMethodNode>>methodComments
by Sean P. DeNigris Oct. 1, 2010

Oct. 1, 2010

Added comment to RBMethodNode>>methodComments indicating that what gets returned is a collection of index intervals, not the actual comment strings http://code.google.com/p/pharo/issues/detail?id=3045 Fix in Inbox: AST-Core-SeanDeNigris.80 -- View this message in context: http://forum.world.st/Issue-3045-DOCUMENTATION-Added-comment-to-RBMethodNod… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 0

[Pharo-project] Issue 3044: Method editor failing
by NicolÃ¡s Paez Oct. 1, 2010

Oct. 1, 2010

*http://code.google.com/p/pharo/issues/detail?id=3044* *Steps to reproduce:* 1. Create a method 2. Declare a temp (i.e. myVariable) 3. Write some code sending a message to a non-existing temp with a name similar to the one you declared (i.e. myVar) 4. Try to save. You should get a suggestion to change myVar -> myVariable. 5. Accept the suggestion 6. Your code will be modify in a wrong way: intead of getting "myVariable" you will get "myVariableiable" Saludos! Nico. blog: nicopaez.wordpress.com

1 0

Oct. 1, 2010

12166 ----- Issue 2943: SUnit 4. Thanks Jannik Laval and Nicolas Anquetil

1 0