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

Re: [Pharo-project] Singleton access selector

by Esteban Lorenzano

On Mon, May 14, 2012 at 9:42 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Mon, May 14, 2012 at 6:24 AM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > >> I've noticed we use a buffet of accessors for singletons, like #default, >> #instance, #current... it'd be nice to just pick one. I like #instance, >> but >> could live with any as long as I never have to guess which one from a list >> again :) >> > > Indeed. For me it depends in the case. For the general case, I like > #uniqueInstance. And #default and #current I use it when it is not > completly singleton. I mean, when there is a class side variable storing > it, but there could be also some other instances, like non-default or > non-current. > +1 > > >> >> Sean >> >> -- >> View this message in context: >> http://forum.world.st/Singleton-access-selector-tp4630062.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > >

May 14, 2012

[Pharo-project] Pharo Kernel job working again

by Pavel Krivanek

Hi, the Pharo Kernel job working again. This two issues are related: http://code.google.com/p/pharo/issues/detail?id=5890&thanks=5890&ts=1336981… http://code.google.com/p/pharo/issues/detail?id=5889&thanks=5889&ts=1336981… Cheers, -- Pavel

May 14, 2012

Re: [Pharo-project] Singleton access selector

by Mariano Martinez Peck

On Mon, May 14, 2012 at 6:24 AM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > I've noticed we use a buffet of accessors for singletons, like #default, > #instance, #current... it'd be nice to just pick one. I like #instance, but > could live with any as long as I never have to guess which one from a list > again :) > Indeed. For me it depends in the case. For the general case, I like #uniqueInstance. And #default and #current I use it when it is not completly singleton. I mean, when there is a class side variable storing it, but there could be also some other instances, like non-default or non-current. > > Sean > > -- > View this message in context: > http://forum.world.st/Singleton-access-selector-tp4630062.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Mariano http://marianopeck.wordpress.com

May 14, 2012

[Pharo-project] [update 2.0] #20073

by Marcus Denker

20073 ----- Issue 5887: Less Sensor hardcoded http://code.google.com/p/pharo/issues/detail?id=5887 Issue 5839: TestRunner Run Coverage fails. http://code.google.com/p/pharo/issues/detail?id=5839 Issue 5876: StringMorphAttributeScanner>>initializeFromStringMorph: http://code.google.com/p/pharo/issues/detail?id=5876 -- Marcus Denker -- http://marcusdenker.de

May 14, 2012

Re: [Pharo-project] [squeak-dev] Fun with spock (NativeBoost FFI)

by Marcus Denker

On May 14, 2012, at 12:49 AM, Igor Stasenko wrote: > On 14 May 2012 00:03, Lawson English <lenglish5(a)cox.net> wrote: >> [pharo-project list added back in] >> >> >> On 5/13/12 1:34 PM, Nicolas Cellier wrote: >>> >>> [100000 primeSwingFactorial] timeToRun 3411 [100000 factorial] timeToRun >>> 61219 So gmp is still 40x faster than a reasonably optimized Smalltalk >>> factorial... I think that's fair, because gmp is highly optimized. Since >>> cost is dominated by LargeInteger arithmetic, and since Smalltalk >>> LargeInteger arithmetic in primitives still operates on bytes, I'm not so >>> surprised of the gap... I'd like to see a 64bit image operating on 32 bits >>> positive integers digits, that would already be a progress... Nicolas >> >> >> For me, the most interesting thing would be to figure out how to integrate >> such external libraries more tightly into the language syntax. >> >> Right now, x := 3.14159... always creates a Float, which is stored as a >> double. >> >> x class ===> Float. >> >> What if I wanted to generate a gmplib floating point number (or rational or >> large integer) automatically when the gmplib binding is available? For Floats, there is a GNU project maintained by some groups at Inria: http://www.mpfr.org/ The main goal of MPFR is to provide a library for multiple-precision floating-point computation which is both efficient and has a well-defined semantics. It copies the good ideas from the ANSI/IEEE-754 standard for double-precision floating-point arithmetic (53-bit significand). -- Marcus Denker -- http://marcusdenker.de

May 14, 2012

Re: [Pharo-project] Semantic Versioning

by Francois Stephany

Thanks for the pointer :) I'm wondering though how that can work in a multi dialects ecosystem. At the moment, a given version can have different dependency depending on your smalltalk dialect/version. Isn't that another dimension of the problem? On 13/05/12 19:45, Sean P. DeNigris wrote: > Do you guys know about this? This seems like it could fit really well with > Metacello... > > http://semver.org/ > > Excerpt: > 'I call this system "Semantic Versioning." Under this scheme, version > numbers and the way they change convey meaning about the underlying code and > what has been modified from one version to the next.' > > -- > View this message in context: http://forum.world.st/Semantic-Versioning-tp4630055.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- http://tulipemoutarde.be CA: +1 778 558 3225 BE: +32 65 709 131

May 14, 2012

Re: [Pharo-project] Singleton access selector

by Nicolas Cellier

To me, default and current suggest these are not singleton, and I wouldn't be surprised to see a specific, previous and next instances. Nicolas 2012/5/14 Sean P. DeNigris <sean(a)clipperadams.com>: > I've noticed we use a buffet of accessors for singletons, like #default, > #instance, #current... it'd be nice to just pick one. I like #instance, but > could live with any as long as I never have to guess which one from a list > again :) > > Sean > > -- > View this message in context: http://forum.world.st/Singleton-access-selector-tp4630062.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

May 14, 2012

[Pharo-project] Singleton access selector

by Sean P. DeNigris

I've noticed we use a buffet of accessors for singletons, like #default, #instance, #current... it'd be nice to just pick one. I like #instance, but could live with any as long as I never have to guess which one from a list again :) Sean -- View this message in context: http://forum.world.st/Singleton-access-selector-tp4630062.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 14, 2012

Re: [Pharo-project] Notify progress with Announcements instead of Exceptions

by Sean P. DeNigris

A few updates... * String>>displayProgressAt:from:to:during: has "deprecated" in the comment, but is not in a deprecated category. The timestamp is 9/7/11 which puts it either 1.2 or early 1.3, but either way, it should be removed for 2.0, right? There is only one sender in the image, which can easily be fixed to call #displayProgressFrom:to:during: * String>>displayProgressFrom:to:during: should probably delegate to the UIManager's displayProgress:from:to:during: * Progress should have its own announcer. The progress could be something that doesn't alter the system, so it doesn't really fit into system announcer. -- View this message in context: http://forum.world.st/Notify-progress-with-Announcements-instead-of-Excepti… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 14, 2012

[Pharo-project] Semantic Versioning

by Sean P. DeNigris

Do you guys know about this? This seems like it could fit really well with Metacello... http://semver.org/ Excerpt: 'I call this system "Semantic Versioning." Under this scheme, version numbers and the way they change convey meaning about the underlying code and what has been modified from one version to the next.' -- View this message in context: http://forum.world.st/Semantic-Versioning-tp4630055.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 14, 2012