June 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] #assert:equals:

by Camillo Bruni

On 2012-06-22, at 09:39, Esteban Lorenzano wrote: > me neither. a=b is clear enough for me. If I want more detail, I add a description. > but perhaps I'm loosing something that I'm not seeing. > > Esteban error messages + inspect??? I hate to go and re-eavluate the code to see what was wrong during comparison... like that you keep the two arguments somewhere up in the stack and you can go and simply go and see what went wrong. consider self assert: self someExpressionReturningFalse = self someExpressionReturningTrue how the heck do you know what went wrong? assert:equals: is the thing to use. I don't like it particularly, it feels too java-ish, I prefer much more the "shoulder" framework written in bern. self someExpressionReturningFalse should = self someExpressionReturningTrue ËËËËËË that somehow feels much more natural to me :P

June 22, 2012

Re: [Pharo-project] #assert:equals:

by Esteban Lorenzano

me neither. a=b is clear enough for me. If I want more detail, I add a description. but perhaps I'm loosing something that I'm not seeing. Esteban On Jun 22, 2012, at 9:35 AM, StÃ©phane Ducasse wrote: > I never understood the problems :) > > Stef > > On Jun 22, 2012, at 3:53 AM, Sean P. DeNigris wrote: > >> This pattern is common in our tests: "self assert: a = b." >> >> I much prefer "self assert: a equals: b." >> >> It makes it easier to diagnose failing tests, especially if a or b are >> expressions with side-effects. Do you agree? >> >> Sean >> >> -- >> View this message in context: http://forum.world.st/assert-equals-tp4636050.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > >

June 22, 2012

Re: [Pharo-project] #assert:equals:

by StÃ©phane Ducasse

I never understood the problems :) Stef On Jun 22, 2012, at 3:53 AM, Sean P. DeNigris wrote: > This pattern is common in our tests: "self assert: a = b." > > I much prefer "self assert: a equals: b." > > It makes it easier to diagnose failing tests, especially if a or b are > expressions with side-effects. Do you agree? > > Sean > > -- > View this message in context: http://forum.world.st/assert-equals-tp4636050.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

June 22, 2012

[Pharo-project] could metacello be hosted on ss3 or smalltalkhub or not load configurationOfHelp?

by StÃ©phane Ducasse

because right now we cannot load configurations because it requires configuration of Help and squeaksource is done. It would be good to have a small version of metacello just loading the bare minimum. Stef

June 22, 2012

Re: [Pharo-project] #assert:equals:

by Mariano Martinez Peck

On Fri, Jun 22, 2012 at 3:53 AM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > This pattern is common in our tests: "self assert: a = b." > > I much prefer "self assert: a equals: b." > > It makes it easier to diagnose failing tests, especially if a or b are > expressions with side-effects. Do you agree? > > I do. I use #assert:equals: in most of my tests. > Sean > > -- > View this message in context: > http://forum.world.st/assert-equals-tp4636050.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Mariano http://marianopeck.wordpress.com

June 22, 2012

[Pharo-project] [update 2.0] #20152

by StÃ©phane Ducasse

20152 ----- - Issue 6105: Spec version 1.0 Thanks Benjamin van Ryseghem . http://code.google.com/p/pharo/issues/detail?id=6105

June 22, 2012

[Pharo-project] How to contribute to Pharo book

by Torsten Bergmann

How can we expect people to contribute to the collabroactive book when the section on "how to contribute" is empty? http://book.pharo-project.org/book/Contribute/ContributeToPharoBook Bye T. -- NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone! Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a

June 22, 2012

Re: [Pharo-project] New System Progress Bar

by phil＠highoctane.be

What about a Progressing Trait? 2012/6/22 Igor Stasenko <siguctua(a)gmail.com> > btw, about human readable.., > i don't understand, why we don't have something as simple as: > > collection do: [... ] showingProgress: 'Processing collection' > (1 to: 100) do: [ ...] showingProgress: 'Processing ' > > 1 to: 100 do: [ ...] showingProgress: 'Processing ' > > i don't care what happens inside, but this interface is IMO much simpler > and straightforward: > a user just adds showingProgress: at the end, and voila, his silent block > now showing a progress. > > -- > Best regards, > Igor Stasenko. > > -- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be| Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges Belgium

June 22, 2012

[Pharo-project] New VMs at http://www.mirandabanda.org/files/Cog/VM/VM.r2559/

by Eliot Miranda

http://www.mirandabanda.org/files/Cog/VM/VM.r2559/ CogVM binaries as per VMMaker.oscog-eem.163/r2559. Make wakeHighestPriority filter-out zombie processes; fixes Newspeak/Glue crash. Add -blockonerror flag to Unix & Mac VMs to allow attaching gdb on error/segv. Make the sigsegv handler catch SIGILL and SIGBUS on Unix and Mac. Add 64-bit file support to linux builds. Fix sqUnixX11.c ClipChildren to ClipByChildren. -- best, Eliot

June 22, 2012

[Pharo-project] #assert:equals:

by Sean P. DeNigris

This pattern is common in our tests: "self assert: a = b." I much prefer "self assert: a equals: b." It makes it easier to diagnose failing tests, especially if a or b are expressions with side-effects. Do you agree? Sean -- View this message in context: http://forum.world.st/assert-equals-tp4636050.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 22, 2012