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

Re: [Pharo-dev] Boolean

by Sven Van Caekenberghe

On 26 Jun 2013, at 14:20, Torsten Bergmann <astares(a)gmx.de> wrote: > Boolean new -> error > Boolean basicNew -> is possible > > should we care? true, false and nil are special since they are unique constant instances, right ? To support that notion, it would seem to be sensible to restrict creating bogus instances. This is already done for #new. But maybe #basicNew for these classes cannot be overridden and is needed somewhere else ? Sven

June 26, 2013

Re: [Pharo-dev] Versions Browser over gitfiletree://

by Esteban A. Maringolo

I like what I see! :) Esteban A. Maringolo 2013/6/26 GOUBIER Thierry <thierry.goubier(a)cea.fr>: > Or ... A first step towards Pharo without a changeset. > > Thierry

June 26, 2013

Re: [Pharo-dev] Metacello doubt

by Dale K. Henrichs

Phil, Check out the System Help ... the API is documented under Metacello>>MetacelloToolBox ... under PrfStef>>Browse tutorials>>Inside Metacello Toolbox there are 5-6 lessons there are other Metacello tutorials there as well ... Dale ----- Original Message ----- | From: phil(a)highoctane.be | To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> | Sent: Wednesday, June 26, 2013 1:45:36 PM | Subject: Re: [Pharo-dev] Metacello doubt | While we are at it, is there any documentation for the | MetacelloToolbox? | Couldn't find... Saw Sean's thing but nothing else. | Would be great! | TIA | Phil | --- | Philippe Back | Dramatic Performance Improvements | Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 | Mail:phil@highoctane.be | Web: http://philippeback.eu | Blog: http://philippeback.be | Twitter: @philippeback | Youtube: http://www.youtube.com/user/philippeback/videos | High Octane SPRL | rue cour Boisacq 101 | 1301 Bierges | Belgium | Featured on the Software Process and Measurement Cast | http://spamcast.libsyn.com | Sparx Systems Enterprise Architect and Ability Engineering EADocX | Value Added Reseller | On Wed, Jun 26, 2013 at 9:21 PM, Dale K. Henrichs < | dale.henrichs(a)gemtalksystems.com > wrote: | | Guido, | | | If the maintainer of a configuration would like to support bleeding | | edge loads that propagate through the dependent projects then they | | should specify which baseline version to use for each dependent | | project. For Native Boost the entry for AsmJit in the #baseline13: | | method could be changed to: | | | project: 'AsmJit' | | | with: [ | | | spec | | | className: 'ConfigurationOfAsmJit'; | | | "==>" versionString: #bleedingEdge; | | | repository: ' http://www.smalltalkhub.com/mc/Pharo/AsmJit/main ' ]; | | | Then the bleedingEdge load would be propagated through to the | | dependents ... but then you'd want the AsmJit configuration | | modified | | as well:) | | | Dale | | | | From: "Guido Chari" < charig(a)gmail.com > | | | | | | To: pharo-dev(a)lists.pharo.org | | | | | | Sent: Wednesday, June 26, 2013 7:27:19 AM | | | | | | Subject: [Pharo-dev] Metacello doubt | | | | | | I have a question since i'm trying to create some jenkins job for | | | the | | | first time. Sorry if this was already discussed... | | | | | | I have a dependency with for example NativeBoost. And i want | | | NativeBoost in its bleedingEdge version. If I "loadBleedingEdge" | | | NativeBoost is on its last version on every package but not its | | | own | | | dependencies as for example AsmJit. Is this the right behavior? | | | How | | | can i express to have not only my dependency but also the | | | dependencies of my dependencies in its bleedingEdge version? | | |

June 26, 2013

Re: [Pharo-dev] Metacello doubt

by Guido Chari

I understood. Thanks for the answer Dale. The drawback in this case is to specify a particular dependency to AsmJit in my configuration. Also, perhaps is the right way since i realized i have a particular dependency on it. But this discussion makes me thing a little and so i have a new question. Form what I (mis) undestand from Metacello, when asking for a bleedingEdge version it loads only the baseline that specifies packages and then last version of every package specified there. As in the projects referenced on the baseline there is no need for specifying a version, and that's the case of nativeBoost configuration, wouldn't it be interesting to have some behavior (i mean i new method for loading like loadDeepSymbolic:) that not only load the symbolicVersion of the package asked, but also propagate that symbolicVersion (bleedingEdge in this case) to all the dependencies that don't specify a concrete version? Guido. 2013/6/26 Dale K. Henrichs <dale.henrichs(a)gemtalksystems.com> > Guido, > > If the maintainer of a configuration would like to support bleeding edge > loads that propagate through the dependent projects then they should > specify which baseline version to use for each dependent project. For > Native Boost the entry for AsmJit in the #baseline13: method could be > changed to: > > project: 'AsmJit' > with: [ > spec > className: 'ConfigurationOfAsmJit'; > "==>" versionString: #bleedingEdge; > repository: ' > http://www.smalltalkhub.com/mc/Pharo/AsmJit/main' ]; > > Then the bleedingEdge load would be propagated through to the dependents > ... but then you'd want the AsmJit configuration modified as well:) > > Dale > > ------------------------------ > > *From: *"Guido Chari" <charig(a)gmail.com> > *To: *pharo-dev(a)lists.pharo.org > *Sent: *Wednesday, June 26, 2013 7:27:19 AM > *Subject: *[Pharo-dev] Metacello doubt > > > I have a question since i'm trying to create some jenkins job for the > first time. Sorry if this was already discussed... > > I have a dependency with for example NativeBoost. And i want NativeBoost > in its bleedingEdge version. If I "loadBleedingEdge" NativeBoost is on its > last version on every package but not its own dependencies as for example > AsmJit. Is this the right behavior? How can i express to have not only my > dependency but also the dependencies of my dependencies in its bleedingEdge > version? > > > > > >

June 26, 2013

Re: [Pharo-dev] Boolean

by Guillermo Polito

On Wed, Jun 26, 2013 at 11:20 PM, Levente Uzonyi <leves(a)elte.hu> wrote: > On Wed, 26 Jun 2013, ClÃ©ment Bera wrote: > > Actually this code: >> True basicNew ifTrue: [ "some code" ] >> works fine on the latest Pharo 3 because of Opal :) >> > > So the Opal compiler lacks important optimizations. :) > Not at all. In fact, the the code is optimized and falls back to the normal lookup in case of exceptional #mustBeBoolean, so the existing code keeps running the same speed ;) > > > Levente > > >> But nice trick for the old compiler :) >> >> >> 2013/6/26 Nicolas Cellier <nicolas.cellier.aka.nice(a)**gmail.com<nicolas.cellier.aka.nice(a)gmail.com> >> > >> Because you don't know the tricks... This one should be just fine >> >> True basicNew ifTrue: [ "some code" ] yourself >> >> >> 2013/6/26 ClÃ©ment Bera <bera.clement(a)gmail.com> >> True basicNew ifTrue: [ "some code" ] >> >> hehe raises NonBooleanReceiver :) >> >> >> 2013/6/26 Camillo Bruni <camillobruni(a)gmail.com> >> why not, let's "forbid" them with an error message! >> >> => maybe you can and error to #become: on nil / true / false as >> well? >> >> On 2013-06-26, at 14:20, Torsten Bergmann <astares(a)gmx.de> wrote: >> >> > Boolean new -> error >> > Boolean basicNew -> is possible >> > >> > should we care? >> > >> >> >> >> >> >> -- >> ClÃ©ment BÃ©raMate Virtual Machine Engineer >> >> BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq >> >> >>

June 26, 2013

Versions Browser over gitfiletree://

by GOUBIER Thierry

Or ... A first step towards Pharo without a changeset. Thierry

June 26, 2013

Re: [Pharo-dev] Boolean

by Levente Uzonyi

On Wed, 26 Jun 2013, ClÃ©ment Bera wrote: > Actually this code:Â > True basicNew ifTrue: [ "some code" ] > works fine on the latest Pharo 3 because of Opal :) So the Opal compiler lacks important optimizations. :) Levente > > But nice trick for the old compiler :) > > > 2013/6/26 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> > Because you don't know the tricks... This one should be just fine > > True basicNew ifTrue: [ "some code" ] yourself > > > 2013/6/26 ClÃ©ment Bera <bera.clement(a)gmail.com> > True basicNew ifTrue: [ "some code" ] > > hehe raises NonBooleanReceiver :) > > > 2013/6/26 Camillo Bruni <camillobruni(a)gmail.com> > why not, let's "forbid" them with an error message! > > => maybe you can and error to #become: on nil / true / false as well? > > On 2013-06-26, at 14:20, Torsten Bergmann <astares(a)gmx.de> wrote: > > > Boolean new Â Â Â Â -> error > > Boolean basicNew Â -> is possible > > > > should we care? > > > > > > > > -- > ClÃ©ment BÃ©raMate Virtual Machine Engineer > BÃ¢timent B 40, avenue Halley 59650Â Villeneuve d'Ascq > > >

June 26, 2013

Re: [Pharo-dev] Boolean

by Esteban A. Maringolo

I guess that once detected adding a Lint rule is better than restrictions everywhere.

June 26, 2013

Re: [Pharo-dev] Metacello doubt

by phil＠highoctane.be

While we are at it, is there any documentation for the MetacelloToolbox? Couldn't find... Saw Sean's thing but nothing else. Would be great! TIA Phil --- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:phil@highoctane.be | Web: http://philippeback.eu Blog: http://philippeback.be | Twitter: @philippeback Youtube: http://www.youtube.com/user/philippeback/videos High Octane SPRL rue cour Boisacq 101 | 1301 Bierges | Belgium Featured on the Software Process and Measurement Cast http://spamcast.libsyn.com Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller On Wed, Jun 26, 2013 at 9:21 PM, Dale K. Henrichs < dale.henrichs(a)gemtalksystems.com> wrote: > Guido, > > If the maintainer of a configuration would like to support bleeding edge > loads that propagate through the dependent projects then they should > specify which baseline version to use for each dependent project. For > Native Boost the entry for AsmJit in the #baseline13: method could be > changed to: > > project: 'AsmJit' > with: [ > spec > className: 'ConfigurationOfAsmJit'; > "==>" versionString: #bleedingEdge; > repository: ' > http://www.smalltalkhub.com/mc/Pharo/AsmJit/main' ]; > > Then the bleedingEdge load would be propagated through to the dependents > ... but then you'd want the AsmJit configuration modified as well:) > > Dale > > ------------------------------ > > *From: *"Guido Chari" <charig(a)gmail.com> > *To: *pharo-dev(a)lists.pharo.org > *Sent: *Wednesday, June 26, 2013 7:27:19 AM > *Subject: *[Pharo-dev] Metacello doubt > > I have a question since i'm trying to create some jenkins job for the > first time. Sorry if this was already discussed... > > I have a dependency with for example NativeBoost. And i want NativeBoost > in its bleedingEdge version. If I "loadBleedingEdge" NativeBoost is on its > last version on every package but not its own dependencies as for example > AsmJit. Is this the right behavior? How can i express to have not only my > dependency but also the dependencies of my dependencies in its bleedingEdge > version? > > > > > >

June 26, 2013

Re: [Pharo-dev] Slide share

by phil＠highoctane.be

This one I can see http://www.slideshare.net/pharoproject/2013-pharo-conference --- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:phil@highoctane.be | Web: http://philippeback.eu Blog: http://philippeback.be | Twitter: @philippeback Youtube: http://www.youtube.com/user/philippeback/videos High Octane SPRL rue cour Boisacq 101 | 1301 Bierges | Belgium Featured on the Software Process and Measurement Cast http://spamcast.libsyn.com Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller On Wed, Jun 26, 2013 at 9:13 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Hi guys > > we created a slideshare acount for pharo > I added > 2009 smalltalks slides > 2011 ESUG > 2013 Pharo Conference > > a new lecture > Intro > Model > Syntax > > http://www.slideshare.net/pharoproject/ > > Can you tell me if you can see the 2013 pharo conference? > Do you know if there are limits on the number of presentations that we can > upload, because > I see (get public on this presentation => go pro). > So I wonder if I want to invest in slideshare. >

June 26, 2013