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

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

by Igor Stasenko

On 2 May 2013 16: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. > it is not the case, when you know the name beforehand. because then why would anyone write 'Smalltalk at: #XXX' while he can just write 'XXX' it is for cases like following: name := self readNameFromSomeExternalSource. (Smalltalk at: name ifPresent: [:cls | cls doSomething) > 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. >>> >>> >> >> >> >> >> > > > -- Best regards, Igor Stasenko.

May 2, 2013

[Pharo-project] sprint relocation

by Camillo Bruni

I am thinking if it makes sense to relocate the sprint to my place... Internet was down every 10mins today and they have problems with the connection here at the lab since a week. Without network we're pretty much dead for a sprint. We've been watching movies at our place with around 20 people, that works. I have a big table (for 10 people or so) a table in my room and 2 more tables. so we might manage to get 2.

May 2, 2013

Re: [Pharo-project] froze image just

by Igor Stasenko

On 2 May 2013 16:39, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 2 May 2013 15:33, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: >> >> On May 2, 2013, at 2:50 PM, Igor Stasenko wrote: >> >>> On 2 May 2013 09:54, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: >>>> What? >>>> I am 99.99% sure it used to interrupt the GUI process if no other viable candidate could be found, why change that? >>>> At least in my mind, if you hit cmd - dot, either you want to interrupt some process blocking the UI on a higher priority, or you want the UI process itself. >>>> For everything else, there's the Process Browser. >>>> >>> >>> It was never like that. >>> It was always looking for a process which is scheduled, but not >>> interrupt process itself. >>> usually that meant it interrupts things like finalization process, >>> so i added logic to avoid interrupting it unless there's nothing else >>> to interrupt. >> >> From 1.4: >> handleUserInterrupt >> [|toInterrupt| >> toInterrupt := Processor preemptedProcess. >> "Only interrupt processes which are potentially blocking the UI" >> toInterrupt priority < UIManager default uiProcess priority ifTrue: [toInterrupt := Project uiProcess]. >> >> So yes, it was like that. >> (barring the other flaws you mentioned, about potentially interrupting critical high-priority processes) >> > Okay, then we need to change #ifNil clause in following method to just > interrupt UI process, > instead of showing useless "not interruptable" message: > > handleUserInterrupt > "This will be called from the event-fetcher process. > Assume no system-vital processes have a lower priority than this, and > are thus ok to interrupt" > UserInterruptHandler cmdDotEnabled ifFalse: [ ^ self ]. > > [ > self processToInterrupt > ifNotNil: [ :proc | proc debugWithTitle: 'User Interrupt' ] > ifNil: [ UIManager default inform: 'Process not interruptable' ] > > "fork exceptions, we don't want interrupt handler to die" > ] on: Error fork: [:ex | ex pass]. > oh.. on second thought, even better.. processToInterrupt "look for best candidate to interrupt: first who is not weak-finalization process and only then weak-finalization process, if nothing left to interrupt. filter out the idle process, since killing it is fatal " | list | list := OrderedCollection new. Processor scanSchedule: [:p | "gather everything but idle process, and processes whose suspendedContext sender == nil, which usually means that process is only scheduled but had no chance to run" ((p ~~ Processor backgroundProcess) and: [ p suspendedContext sender notNil ]) ifTrue: [ list add: p ] ] startingAt: Processor activePriority. "now answer first process in list, skipping the finalization process" list do: [:p | p == WeakArray runningFinalizationProcess ifFalse: [ ^ p ] ]. "now answer first process , if any ,otherwise answer ui process by default" ^ list isEmpty ifTrue: [ UIManager default uiProcess ] ifFalse: [ list first ] so it interrupts even if i do 1 hour wait in workspace >> Cheers, >> Henry > > > > -- > Best regards, > Igor Stasenko. -- Best regards, Igor Stasenko.

May 2, 2013

[Pharo-project] [regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=ma… 3 regressions found. KernelTests.Objects.UndefinedObjectTest.testStoreOn Multilingual.Tests.TextConversion.UTF16TextConverterTest.testBOMWrite Multilingual.Tests.TextConversion.UTF16TextConverterTest.testNoBOMWriteInMiddleOfFile

May 2, 2013

Re: [Pharo-project] froze image just

by Igor Stasenko

On 2 May 2013 15:33, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > > On May 2, 2013, at 2:50 PM, Igor Stasenko wrote: > >> On 2 May 2013 09:54, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: >>> What? >>> I am 99.99% sure it used to interrupt the GUI process if no other viable candidate could be found, why change that? >>> At least in my mind, if you hit cmd - dot, either you want to interrupt some process blocking the UI on a higher priority, or you want the UI process itself. >>> For everything else, there's the Process Browser. >>> >> >> It was never like that. >> It was always looking for a process which is scheduled, but not >> interrupt process itself. >> usually that meant it interrupts things like finalization process, >> so i added logic to avoid interrupting it unless there's nothing else >> to interrupt. > > From 1.4: > handleUserInterrupt > [|toInterrupt| > toInterrupt := Processor preemptedProcess. > "Only interrupt processes which are potentially blocking the UI" > toInterrupt priority < UIManager default uiProcess priority ifTrue: [toInterrupt := Project uiProcess]. > > So yes, it was like that. > (barring the other flaws you mentioned, about potentially interrupting critical high-priority processes) > Okay, then we need to change #ifNil clause in following method to just interrupt UI process, instead of showing useless "not interruptable" message: handleUserInterrupt "This will be called from the event-fetcher process. Assume no system-vital processes have a lower priority than this, and are thus ok to interrupt" UserInterruptHandler cmdDotEnabled ifFalse: [ ^ self ]. [ self processToInterrupt ifNotNil: [ :proc | proc debugWithTitle: 'User Interrupt' ] ifNil: [ UIManager default inform: 'Process not interruptable' ] "fork exceptions, we don't want interrupt handler to die" ] on: Error fork: [:ex | ex pass]. > Cheers, > Henry -- Best regards, Igor Stasenko.

May 2, 2013

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

by Ben Coman

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. 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

[Pharo-project] [regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=wi… 3 regressions found. KernelTests.Objects.UndefinedObjectTest.testStoreOn Multilingual.Tests.TextConversion.UTF16TextConverterTest.testBOMWrite Multilingual.Tests.TextConversion.UTF16TextConverterTest.testNoBOMWriteInMiddleOfFile

May 2, 2013

[Pharo-project] [regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=li… 3 regressions found. KernelTests.Objects.UndefinedObjectTest.testStoreOn Multilingual.Tests.TextConversion.UTF16TextConverterTest.testBOMWrite Multilingual.Tests.TextConversion.UTF16TextConverterTest.testNoBOMWriteInMiddleOfFile

May 2, 2013

[Pharo-project] [update 3.0] #30084

by Marcus Denker

May 2, 2013

[Pharo-project] Unix socket plugin patch for systemd

by Max Leske

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? Cheers, Max

May 2, 2013