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

Re: [Pharo-project] sprint image preparation

by Igor Stasenko

On 2 May 2013 19:28, Camillo Bruni <camillobruni(a)gmail.com> wrote: > Could we upload a new version of the latest image with all the > DateAndTime delays removed? I think that would be nice for the > sprint tomorrow. > > I can do it later this evening, unless some special care is > needed for that? > i did not finished cleaning up the code in my refactoring (and this is what planned to do for sprint). however the image with changes i made works for 2nd week without any problems so far :) -- Best regards, Igor Stasenko.

May 2, 2013

[Pharo-project] sprint image preparation

by Camillo Bruni

Could we upload a new version of the latest image with all the DateAndTime delays removed? I think that would be nice for the sprint tomorrow. I can do it later this evening, unless some special care is needed for that?

May 2, 2013

Re: [Pharo-project] How i can retrieve the global by its name?

by Igor Stasenko

On 2 May 2013 18:40, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > #bindedXXX and #boundXXX sounds pretty static to me... It's like it was > already binded. And maybe in the back it is dynamically looked up. Maybe a > more abstract name can fit better: > > #resolveToClass ? #lookupClass ? > > Also (I'm pretty negative today), let's do not forget about traits! (We > always do, and that gives us problems later ) > that's why i said that whatever name you give to the method, if it ends with "class" then it should either answer a valid class or fail. In opposite to #symbol asGlobal which should fail only if such global not found. e.g.: asClass | cls | cls := self asGlobal. cls isClass ifFalse: [ self error: 'no way']. ^ cls > > On Thu, May 2, 2013 at 6:33 PM, Chris Cunningham <cunningham.cb(a)gmail.com> > wrote: >> >> On Thu, May 2, 2013 at 9:29 AM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >>> >>> >>> #bindedClass >>> #bindedClassOn: anEnvironment >>> >>> looks clearer to me. >>> >>> Esteban >> >> maybe: >> #boundClass >> #boundClassOn: anEnvironment >> > -- Best regards, Igor Stasenko.

May 2, 2013

Re: [Pharo-project] How i can retrieve the global by its name?

by Guillermo Polito

#bindedXXX and #boundXXX sounds pretty static to me... It's like it was already binded. And maybe in the back it is dynamically looked up. Maybe a more abstract name can fit better: #resolveToClass ? #lookupClass ? Also (I'm pretty negative today), let's do not forget about traits! (We always do, and that gives us problems later ) On Thu, May 2, 2013 at 6:33 PM, Chris Cunningham <cunningham.cb(a)gmail.com>wrote: > On Thu, May 2, 2013 at 9:29 AM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > >> >> #bindedClass >> #bindedClassOn: anEnvironment >> >> looks clearer to me. >> >> Esteban >> > maybe: > #boundClass > #boundClassOn: anEnvironment > >

May 2, 2013

Re: [Pharo-project] How i can retrieve the global by its name?

by Chris Cunningham

On Thu, May 2, 2013 at 9:29 AM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > > #bindedClass > #bindedClassOn: anEnvironment > > looks clearer to me. > > Esteban > maybe: #boundClass #boundClassOn: anEnvironment

May 2, 2013

Re: [Pharo-project] How i can retrieve the global by its name?

by Esteban Lorenzano

the problem with #bind is that a binding is a pair (an association), not its value... so it can cause confusion (and you know murphy's law: it it can, it will). #asClass is not so bad #asClassOn: anEnvironment can work too. or: #bindedClass #bindedClassOn: anEnvironment looks clearer to me. Esteban On May 2, 2013, at 5:49 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > I vote for the #bind* (ej, #bindToClass) or similar. > > The #asX... means casting for me. > > I'd expect that `#Foo asClass` answer a new class named #Foo. > > Regards, > Esteban A. Maringolo > > > 2013/5/2 Igor Stasenko <siguctua(a)gmail.com>: >> On 2 May 2013 16:56, Frank Shearar <frank.shearar(a)gmail.com> wrote: >>> On 2 May 2013 15:37, Ben Coman <btc(a)openinworld.com> wrote: >>>> Sven Van Caekenberghe wrote: >>>>> >>>>> On 02 May 2013, at 06:03, Igor Stasenko <siguctua(a)gmail.com> wrote: >>>>> >>>>> >>>>>> >>>>>> Hi, all >>>>>> >>>>>> do not think that i am drunk or vent crazy, asking such silly >>>>>> question, which at best should be asked only by beginner :) >>>>>> >>>>>> I know the answer: >>>>>> >>>>>> Smalltalk at: #SomeName >>>>>> >>>>>> or >>>>>> >>>>>> Smalltalk globals at: #SomeName >>>>>> >>>>>> what stroke me, just now, that both answers is wrong! >>>>>> >>>>>> It should be: >>>>>> >>>>>> #SomeName asGlobal >>>>>> >>>>>> (or suggest more appropriate/precise method name for a symbol) >>>>>> >>>>> >>>>> >>>>> ConfigurationOfXYZ globalValue project bleedingEdge load. >>>>> >>>>> ConfigurationOfXYZ globalValueIfPresent: [ :configuration | configuration >>>>> project bleedingEdge load ] >>>>> >>>>> An alternative could be globalBinding, but that is more technical. >>>>> >>>>> #asGlobal sounds like a conversion, on the other hand it is an accepted >>>>> idiom. >>>>> >>>> >>>> >>>> #asGlobal feels confusing to me. It doesn't sound like a lookup. Some >>>> other alternatives: >>>> >>>> #SomeName fromGlobal >>>> #SomeName from: someOtherEnvironment >>>> >>>> #SomeName fromEnvironment "the current one" >>>> #SomeName fromEnvironment: someOtherEnvironment >>>> >>>> #SomeName fromEnv: someOtherEnvironment >>>> #SomeName fromEnv "the current one" >>>> >>>> >>>> but why bother at all. What is the advantage over this: >>>> >>>> Smalltalk at: #xx put: 1. >>>> xx inspect. >>> >>> But the use case here is when you want to reference a class that has >>> not yet been loaded, which happens every time you run a load script >>> for a ConfigurationOf. >>> >> yes, so you write: >> >> #ConfigurationOfXYZ asClass load. >> >> instead of: >> >> (Smalltalk at: #ConfigurationOfXYZ) load. >> >> >>> frank >> >> >> -- >> Best regards, >> Igor Stasenko. >> >

May 2, 2013

Re: [Pharo-project] How i can retrieve the global by its name?

by Esteban A. Maringolo

I vote for the #bind* (ej, #bindToClass) or similar. The #asX... means casting for me. I'd expect that `#Foo asClass` answer a new class named #Foo. Regards, Esteban A. Maringolo 2013/5/2 Igor Stasenko <siguctua(a)gmail.com>: > On 2 May 2013 16:56, Frank Shearar <frank.shearar(a)gmail.com> wrote: >> On 2 May 2013 15:37, Ben Coman <btc(a)openinworld.com> wrote: >>> Sven Van Caekenberghe wrote: >>>> >>>> On 02 May 2013, at 06:03, Igor Stasenko <siguctua(a)gmail.com> wrote: >>>> >>>> >>>>> >>>>> Hi, all >>>>> >>>>> do not think that i am drunk or vent crazy, asking such silly >>>>> question, which at best should be asked only by beginner :) >>>>> >>>>> I know the answer: >>>>> >>>>> Smalltalk at: #SomeName >>>>> >>>>> or >>>>> >>>>> Smalltalk globals at: #SomeName >>>>> >>>>> what stroke me, just now, that both answers is wrong! >>>>> >>>>> It should be: >>>>> >>>>> #SomeName asGlobal >>>>> >>>>> (or suggest more appropriate/precise method name for a symbol) >>>>> >>>> >>>> >>>> ConfigurationOfXYZ globalValue project bleedingEdge load. >>>> >>>> ConfigurationOfXYZ globalValueIfPresent: [ :configuration | configuration >>>> project bleedingEdge load ] >>>> >>>> An alternative could be globalBinding, but that is more technical. >>>> >>>> #asGlobal sounds like a conversion, on the other hand it is an accepted >>>> idiom. >>>> >>> >>> >>> #asGlobal feels confusing to me. It doesn't sound like a lookup. Some >>> other alternatives: >>> >>> #SomeName fromGlobal >>> #SomeName from: someOtherEnvironment >>> >>> #SomeName fromEnvironment "the current one" >>> #SomeName fromEnvironment: someOtherEnvironment >>> >>> #SomeName fromEnv: someOtherEnvironment >>> #SomeName fromEnv "the current one" >>> >>> >>> but why bother at all. What is the advantage over this: >>> >>> Smalltalk at: #xx put: 1. >>> xx inspect. >> >> But the use case here is when you want to reference a class that has >> not yet been loaded, which happens every time you run a load script >> for a ConfigurationOf. >> > yes, so you write: > > #ConfigurationOfXYZ asClass load. > > instead of: > > (Smalltalk at: #ConfigurationOfXYZ) load. > > >> frank > > > -- > Best regards, > Igor Stasenko. >

May 2, 2013

Re: [Pharo-project] How i can retrieve the global by its name?

by Igor Stasenko

On 2 May 2013 16:56, Frank Shearar <frank.shearar(a)gmail.com> wrote: > On 2 May 2013 15:37, Ben Coman <btc(a)openinworld.com> wrote: >> Sven Van Caekenberghe wrote: >>> >>> On 02 May 2013, at 06:03, Igor Stasenko <siguctua(a)gmail.com> wrote: >>> >>> >>>> >>>> Hi, all >>>> >>>> do not think that i am drunk or vent crazy, asking such silly >>>> question, which at best should be asked only by beginner :) >>>> >>>> I know the answer: >>>> >>>> Smalltalk at: #SomeName >>>> >>>> or >>>> >>>> Smalltalk globals at: #SomeName >>>> >>>> what stroke me, just now, that both answers is wrong! >>>> >>>> It should be: >>>> >>>> #SomeName asGlobal >>>> >>>> (or suggest more appropriate/precise method name for a symbol) >>>> >>> >>> >>> ConfigurationOfXYZ globalValue project bleedingEdge load. >>> >>> ConfigurationOfXYZ globalValueIfPresent: [ :configuration | configuration >>> project bleedingEdge load ] >>> >>> An alternative could be globalBinding, but that is more technical. >>> >>> #asGlobal sounds like a conversion, on the other hand it is an accepted >>> idiom. >>> >> >> >> #asGlobal feels confusing to me. It doesn't sound like a lookup. Some >> other alternatives: >> >> #SomeName fromGlobal >> #SomeName from: someOtherEnvironment >> >> #SomeName fromEnvironment "the current one" >> #SomeName fromEnvironment: someOtherEnvironment >> >> #SomeName fromEnv: someOtherEnvironment >> #SomeName fromEnv "the current one" >> >> >> but why bother at all. What is the advantage over this: >> >> Smalltalk at: #xx put: 1. >> xx inspect. > > But the use case here is when you want to reference a class that has > not yet been loaded, which happens every time you run a load script > for a ConfigurationOf. > yes, so you write: #ConfigurationOfXYZ asClass load. instead of: (Smalltalk at: #ConfigurationOfXYZ) load. > frank -- Best regards, Igor Stasenko.

May 2, 2013

Re: [Pharo-project] How i can retrieve the global by its name?

by Frank Shearar

On 2 May 2013 15:37, Ben Coman <btc(a)openinworld.com> wrote: > Sven Van Caekenberghe wrote: >> >> On 02 May 2013, at 06:03, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> >>> >>> Hi, all >>> >>> do not think that i am drunk or vent crazy, asking such silly >>> question, which at best should be asked only by beginner :) >>> >>> I know the answer: >>> >>> Smalltalk at: #SomeName >>> >>> or >>> >>> Smalltalk globals at: #SomeName >>> >>> what stroke me, just now, that both answers is wrong! >>> >>> It should be: >>> >>> #SomeName asGlobal >>> >>> (or suggest more appropriate/precise method name for a symbol) >>> >> >> >> ConfigurationOfXYZ globalValue project bleedingEdge load. >> >> ConfigurationOfXYZ globalValueIfPresent: [ :configuration | configuration >> project bleedingEdge load ] >> >> An alternative could be globalBinding, but that is more technical. >> >> #asGlobal sounds like a conversion, on the other hand it is an accepted >> idiom. >> > > > #asGlobal feels confusing to me. It doesn't sound like a lookup. Some > other alternatives: > > #SomeName fromGlobal > #SomeName from: someOtherEnvironment > > #SomeName fromEnvironment "the current one" > #SomeName fromEnvironment: someOtherEnvironment > > #SomeName fromEnv: someOtherEnvironment > #SomeName fromEnv "the current one" > > > but why bother at all. What is the advantage over this: > > Smalltalk at: #xx put: 1. > xx inspect. But the use case here is when you want to reference a class that has not yet been loaded, which happens every time you run a load script for a ConfigurationOf. frank > cheers -ben > > >> >>> >>> optionally, we could also have one, with handling absent case: >>> >>> #SomeName asGlobalIfAbsent: [] >>> >>> same , but only if present: >>> >>> #SomeName asGlobalIfPresent: [:global | ] >>> >>> >>> Currently, there is 941 references to 'Smalltalk' global in my pharo >>> image. >>> If we introduce this convenience method, it will shrink this number >>> considerably, >>> not saying that code will be more elegant and concise compare: >>> >>> (Smalltalk globals at: #Foo) doSomething >>> >>> and >>> >>> #Foo asGlobal doSomething >>> >>> P.S. What really strikes me is why we don't have such method from very >>> beginning, >>> and instead refer to 'Smalltalk' all over the places. >>> Some things are so deeply indoctrinated in our minds, that we don't >>> even think that it can be different. >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >>> >> >> >> >> >> > > >

May 2, 2013

Re: [Pharo-project] [squeak-dev] Unix socket plugin patch for systemd

by Max Leske

Thanks Bert. On 02.05.2013, at 16:29, Bert Freudenberg <bert(a)freudenbergs.de> wrote: > On 2013-05-02, at 15:44, Max Leske <maxleske(a)gmail.com> wrote: > >> We've created a patch for the unix socket plugin that allows for socket activation via systemd. >> >> This is how it works: >> 1. tell systemd to link a socket to the vm (e.g. 8080) >> 2. send a request to the socket >> 3. systemd will launch the vm and hold the request until the image is connected to the port >> 4. (here's where the patch comes in) connect to the socket in the image (e.g. by starting WAKom - WAKom startOn: 8080) >> >> The patch is necessary because the primitive would fail when connecting to the socket (the plugin thinks that the socket is already in use). >> >> So here's my question: who is responsible for the plugin or would like to integrate the patch? > > > Send it to vm-dev, the responsible people hang out there. And cc Ian and Eliot explicitly. > > - Bert - > >

May 2, 2013