- Pharo-dev - lists.pharo.org

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

by S Krish

Yes that's a much needed one. I used it yesterday, after creating my own crOut, I quickly looked into Pharo2.0 to find these crLog, logCr et als.. Beginner stuff like this does make it lot easier for everyone, not just beginners..! We could borrow from all other languages if any like this.. On Thu, May 2, 2013 at 12:21 PM, stephane ducasse <stephane.ducasse(a)free.fr>wrote: > + 1 > Let's propose a nice protocal and we use the rewrite tool for real! > This is also why I want > crLog > instead of Transcript show: > > Stef > > > 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) > > > > 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] How i can retrieve the global by its name?

by Frank Shearar

What's "global"? Even if you haven't implemented scoped environments, rather use a name that doesn't imply that you'll never have scoped environments. #asClass sounds better, except for Guillermo's point about well-known things that aren't classes. frank On 2 May 2013 09:31, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > Sounds a bit like VW #{ } > > This sounds good to me, but don't use globalBinding, I would expect this one > to answer the binding (Asociation) rather than the value. > > > 2013/5/2 Sven Van Caekenberghe <sven(a)stfx.eu> >> >> >> 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. >> >> > 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] How i can retrieve the global by its name?

by Nicolas Cellier

Sounds a bit like VW #{ } This sounds good to me, but don't use globalBinding, I would expect this one to answer the binding (Asociation) rather than the value. 2013/5/2 Sven Van Caekenberghe <sven(a)stfx.eu> > > 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. > > > 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] How i can retrieve the global by its name?

by Guillermo Polito

+1!! The only thing that makes me noise about asClass is #Processor asClass #Transcript asClass What do we do with those guys? :) On Thu, May 2, 2013 at 9:17 AM, Camillo Bruni <camillobruni(a)gmail.com>wrote: > > On 2013-05-02, at 09:12, Sven Van Caekenberghe <sven(a)stfx.eu> 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. > > I would go with #asGlobal, though I'd prefer something like #asClass since > I do not believe in anything but classes in SmalltalkDictionary :P, well > we can add both can we :) >

May 2, 2013

[Pharo-project] [update 3.0] #30082

by Marcus Denker

May 2, 2013

Re: [Pharo-project] SUnit design question

by Herby VojÄÃk

In Amber I created such thing, for the same reasons, but there SUnit is lot simpler than Pharo's one. stephane ducasse wrote: > Indeed it would be nice to have. > > On May 1, 2013, at 11:29 AM, Camillo Bruni<camillobruni(a)gmail.com> wrote: > >> I'm not sure if I asked that question before, but why is there no >> dedicated TestRunner model in SUnit? (detailed question further down) >> >> There is a TestRunner but that is clearly a UI part. >> >> We have right now 2 places in the system where that would come in >> handy: HDTestReport and the CommandLineTestRunner. >> >> Both places modify the output of the test runner, so to say instrument >> the test runs. >> >> see http://stackoverflow.com/questions/16315726/how-do-i-instrument-test-runner… > >

May 2, 2013

Re: [Pharo-project] froze image just

by Henrik Johansen

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. Cheers, Henry On May 1, 2013, at 2:31 AM, Igor Stasenko wrote: > On 30 April 2013 22:44, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> trying to publish a slice on my harddisc without networkâ¦. >> and I could not interrupt anything. >> No cmd+. no interdiction sign did anything :( >> >> So is it normal? >> Not being able to interrupt something is a pain. >> >> stef > > the problem stems from the point that when you press cmd+. > an interrupt process logic looking for some other active process > to stop it.. > now since UI process blocked by semaphore, as well as rest, > it finds nothing to interrupt and ignores it :) > > i think we should think about it, like putting synthesized context > with '1halt', to UI process, so when it will awake, it will be halted. > > Or... if interrupt handler found nothing, then always spawn new UI process > opening debugger on old one. > > -- > Best regards, > Igor Stasenko. >

May 2, 2013

Re: [Pharo-project] froze image just

by Sven Van Caekenberghe

On 02 May 2013, at 09:01, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > 2013/5/2 Camillo Bruni <camillobruni(a)gmail.com> > > On 2013-05-02, at 08:36, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > > Same problem in same train situation. > > I press commit on local directory and system start connect to smalltalkhub > > repository and hang for ever. Why system doing this when I use local > > repository? > > Because MC has some limitations :). If you commit a package that is by > default in Pharo you'll always have the Pharo30 repository there. So > when you commit MC tries to be smart and gather a unique version number > by checking ALL repositories ... there is your issue :( > > > It makes offline work impossible. Can we add setting for this? Yes, there should be a setting that says: 'MC should not check other repositories for potential conflicts when saving'. It is a lot faster when you do have network as well. Sven

May 2, 2013

Re: [Pharo-project] froze image just

by Camillo Bruni

On 2013-05-02, at 09:01, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > 2013/5/2 Camillo Bruni <camillobruni(a)gmail.com> >> On 2013-05-02, at 08:36, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >> >>> Same problem in same train situation. >>> I press commit on local directory and system start connect to >> smalltalkhub >>> repository and hang for ever. Why system doing this when I use local >>> repository? >> >> Because MC has some limitations :). If you commit a package that is by >> default in Pharo you'll always have the Pharo30 repository there. So >> when you commit MC tries to be smart and gather a unique version number >> by checking ALL repositories ... there is your issue :( >> > It makes offline work impossible. Can we add setting for this? yes I know. Humm yeah, I guess we could solve this by having setting to disable the "global" unique version number check...

May 2, 2013

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

by Camillo Bruni

On 2013-05-02, at 09:12, Sven Van Caekenberghe <sven(a)stfx.eu> 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. I would go with #asGlobal, though I'd prefer something like #asClass since I do not believe in anything but classes in SmalltalkDictionary :P, well we can add both can we :)

May 2, 2013