- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] New methods for the String class

by phil＠highoctane.be

Which Ruby guru an Python guru is going to give it a shot? [I am a Tcl guy... hey, that's an everything is a string language... ] Oh well, I started something: http://www.smalltalkhub.com/#!/~philippeback/StringTclShim So, who is taking StringRubyShim and StringPythonShim :-p ? Phil On Wed, Feb 26, 2014 at 5:09 PM, Camillo Bruni <camillobruni(a)gmail.com>wrote: > > On 2014-02-26, at 03:53, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> > wrote: > > > > > > > > > 2014-02-25 8:49 GMT-03:00 phil(a)highoctane.be <phil(a)highoctane.be>: > > Yes but... in Pharo strings are collections and a ton of things can be > done with collections already. > > Other languages have more "basic" strings and are cutting them in all > ways possible but not as collections. > > > > things like detect, inject etc are not really in the repertoire of other > languages. Okay, there are chop, split, ... but these are pretty basic > things. > > > > Why not have a test suite with a test for demonstrating how to do these > things with the platform we do have? > > > > e.g. testChomp, testSplit, ...all put in a Tests-Strings-RubyStyle or > Tests-Strings-PythonStyle packages? > > > > And like there are Seaside-Pharo-XXX packages, why not a > String-Ruby-XXXX thing ? > > > > > > Yes, that is a really good idea. > > indeed, we can do it in two steps: > > 1. create the ruby / pythonic compatibility packages (blindly ignoring any > pharo conventions) > 2. see which methods (if any) actually make sense to steal >

Feb. 26, 2014

Re: [Pharo-dev] access to CI debug info Re: test failures in downloaded image 30733

by btc＠openinworld.com

Feb. 26, 2014

Re: [Pharo-dev] In Praise of Small Commits | Dr Dobb's

by Pharo4Stef

+1 000000 S On 26 Feb 2014, at 09:57, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > http://www.drdobbs.com/architecture-and-design/in-praise-of-small-commits/2… > > << With smaller commits, teams accelerate code reviews and builds, while shrinking the delay between committing and feedback. That's a lot of payback for a simple practice. >> > > From an integration standpoint, I love small and clean Slices. > > Sven > > > >

Feb. 26, 2014

Re: [Pharo-dev] Stepping through with GLORP Proxies

by Esteban A. Maringolo

Hi Eliot, 2013-11-30 18:30 GMT-03:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > On Fri, Nov 29, 2013 at 2:22 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> > wrote: >> 2013/11/29 Eliot Miranda <eliot.miranda(a)gmail.com>: >> > I'll either prepare a change set or submit. It'll get done. >> I can continue stepping into until the change is ready. >> Please make it compatible with Pharo 2 (whatever that means in term of >> code) :) > > > OK, the code is now in Squeak trunk. What image should I use to integrate > into Pharo 2? A url please... I'm coming back late to this. Because the change wasn't integrated in Pharo 2. Do you have the changeset applied to Squeak Trunk? I'd like to reapply it in my Pharo 2 image (at my own risk). Can you send it to may email address? Thank you! Esteban A. Maringolo

Feb. 26, 2014

Re: [Pharo-dev] Pharo 3.0 on Windows 8.1

by Sven Van Caekenberghe

On 26 Feb 2014, at 17:21, btc(a)openinworld.com wrote: > Nice initiative - but up to about 50 seconds the image is so compressed it is unreadable. > cheers -ben No, it's not. The movie is properly HD, 720p (1280 px Ã 720 px). YouTube automatically adapts the quality setting depending on the quality of your connection. It probably started with a lower quality settings and switched half way. > Sven Van Caekenberghe wrote: >> Pharo 3.0 on Windows 8.1 >> Installing and running Pharo 3.0 on a blank Windows 8.1 machine in under 1 minute. >> >> http://www.youtube.com/watch?v=FKokxrQtrg0 >> >> With an extra minute to demo some elementary interactions. >> >> Sven >> >> -- >> Sven Van Caekenberghe >> Proudly supporting Pharo >> http://pharo.org >> http://association.pharo.org >> http://consortium.pharo.org >> >> >> >> >> >> >> > >

Feb. 26, 2014

Re: [Pharo-dev] Pharo 3.0 on Windows 8.1

by btc＠openinworld.com

Nice initiative - but up to about 50 seconds the image is so compressed it is unreadable. cheers -ben Sven Van Caekenberghe wrote: > Pharo 3.0 on Windows 8.1 > > Installing and running Pharo 3.0 on a blank Windows 8.1 machine in under 1 minute. > > http://www.youtube.com/watch?v=FKokxrQtrg0 > > With an extra minute to demo some elementary interactions. > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > > > >

Feb. 26, 2014

Re: [Pharo-dev] New methods for the String class

by Camillo Bruni

On 2014-02-26, at 03:53, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > > > 2014-02-25 8:49 GMT-03:00 phil(a)highoctane.be <phil(a)highoctane.be>: > Yes but... in Pharo strings are collections and a ton of things can be done with collections already. > Other languages have more "basic" strings and are cutting them in all ways possible but not as collections. > > things like detect, inject etc are not really in the repertoire of other languages. Okay, there are chop, split, ... but these are pretty basic things. > > Why not have a test suite with a test for demonstrating how to do these things with the platform we do have? > > e.g. testChomp, testSplit, ...all put in a Tests-Strings-RubyStyle or Tests-Strings-PythonStyle packages? > > And like there are Seaside-Pharo-XXX packages, why not a String-Ruby-XXXX thing ? > > > Yes, that is a really good idea. indeed, we can do it in two steps: 1. create the ruby / pythonic compatibility packages (blindly ignoring any pharo conventions) 2. see which methods (if any) actually make sense to steal

Feb. 26, 2014

Re: [Pharo-dev] expected failures

by Camillo Bruni

On 2014-02-25, at 17:04, btc(a)openinworld.com wrote: > I'd like to better understand the semantics of "expected failures" in TestRunner. It seems to me that if you want to ensure that a certain operation fails, in a test you'd wrap it as follows... > > shouldFailed=false. > [ self operationThatShouldFail ] on: Error do: [ shouldFailed := true ]. > self assert: shouldFailed. I prefer: self should: [ self operationThatShouldFail ] raise: ASpecificError Otherwise you can just run the code itself: self operationThatShouldFail the test framework will take care of it and mark the test correctly as a failure.

Feb. 26, 2014

Re: [Pharo-dev] [Pharo-users] Pharo 3.0 on Windows 8.1

by Tudor Girba

Beautiful! Doru On Wed, Feb 26, 2014 at 3:47 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Pharo 3.0 on Windows 8.1 > > Installing and running Pharo 3.0 on a blank Windows 8.1 machine in under 1 > minute. > > http://www.youtube.com/watch?v=FKokxrQtrg0 > > With an extra minute to demo some elementary interactions. > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 26, 2014

Pharo 3.0 on Windows 8.1

by Sven Van Caekenberghe

Pharo 3.0 on Windows 8.1 Installing and running Pharo 3.0 on a blank Windows 8.1 machine in under 1 minute. http://www.youtube.com/watch?v=FKokxrQtrg0 With an extra minute to demo some basic interactions. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

Feb. 26, 2014