- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

by Sven Van Caekenberghe

Thanks for the (positive) feedback. My problem is: if you think this through, lots of things could change. Consider that I added #magnitudes this would imply that sorting should move too, because you cannot assume the objects to be sortable (i.e. Magnitudes or conforming to that protocol). Also, this would create a kind of parallel hierarchy, with more type information. It feels like a simple single inheritance hierarchy cannot cover all combinations (for example, being sequenceable and being numbers, as opposed to being just a collection of numbers). Sorting an unordered collection is also different from sorting an ordered one (this last one could keep its type, or even be sorted in place). So maybe this is a can of worms. I am all for dynamic typing, not for trying to add some (weak) for of static typing. > On 07 Jan 2016, at 13:14, Max Leske <maxleske(a)gmail.com> wrote: > > Very, very cool Sven (and Henrik!)! > > And it even works with exotic objects: { 1@2. 2@3 } numbers sum ââ> (3@5)â > > Could Collections-Arithmetic be integrated into the collections operations? Not really sure thatâs a good idea, I just want to know. > > Cheers, > Max > >> On 04 Jan 2016, at 16:19, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Thank you, Sven! >> >> I like this very much. >> >> This would also mean that we could deprecate Collection>>#sum altogether :)) >> >> Cheers, >> Doru >> >> >>> On Dec 30, 2015, at 12:53 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> Hi Henrik, >>> >>>> On 25 Dec 2015, at 14:08, Henrik Nergaard <henrin10(a)student.uia.no> wrote: >>>> >>>> Like this? >>>> http://smalltalkhub.com/#!/~Latsabben/NumIt >>> >>> That is a cool take on a possible approach. Thanks for doing it, it makes it much easier to think about and discuss alternatives. >>> >>> This inspired me to do something similar, but not quite. I am just thinking out loud by implementation. Here is my result: >>> >>> <Collections-Operations-SvenVanCaekenberghe.1.mcz> >>> >>> There are some examples in the class comments. >>> >>> Sven >>> >>>> Best regards, >>>> Henrik >>>> >>>> -----Original Message----- >>>> From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of stepharo >>>> Sent: Thursday, December 24, 2015 9:58 AM >>>> To: Pharo Development List <pharo-dev(a)lists.pharo.org> >>>> Subject: Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers: >>>> >>>> Just a remark. >>>> I think that we discarded the proposition of having >>>> >>>> aCol arithmetic sum >>>> >>>> but I found it nice because there if was clear that you want to get back >>>> 0 for #(). >>>> >>>> Stef >>>> >>> >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Innovation comes in the least expected form. >> That is, if it is expected, it already happened." >> >> > >

Jan. 7, 2016

Re: [Pharo-dev] ifError: implementation is bad

by Denis Kudriashov

2016-01-07 13:35 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > If think it makes more sense to #cull: the exception instance, it is more > object oriented We all know it. But then we found such methods in the system and cry :). who can wrote it

Jan. 7, 2016

Re: [Pharo-dev] ifError: implementation is bad

by Sven Van Caekenberghe

> On 07 Jan 2016, at 13:11, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi > > I look at implementation of BlockClosure>>ifError: . I did't know that it culls arguments to errorBlock. > But what is this arguments? It is not error instance but specific properties from it. > > BlockClosure>>ifError: errorHandlerBlock > > ^ self on: Error do: [:ex | > errorHandlerBlock cull: ex description cull: ex receiver] > > Why people doing that? > Many users of it just pass given error like > > [...] ifError: [:msg :rcv | ... > rcv error: msg]. > > Especially it is commonly used scenario by senders of #critical:ifError:. But it is different question. > > I propose change ifError: to cull error instance. > > What you think? Can be put it in Pharo 5? Such change can touch some packages If think it makes more sense to #cull: the exception instance, it is more object oriented. And it is what I would expect.

Jan. 7, 2016

Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

by Max Leske

Very, very cool Sven (and Henrik!)! And it even works with exotic objects: { 1@2. 2@3 } numbers sum ââ> (3@5)â Could Collections-Arithmetic be integrated into the collections operations? Not really sure thatâs a good idea, I just want to know. Cheers, Max > On 04 Jan 2016, at 16:19, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Thank you, Sven! > > I like this very much. > > This would also mean that we could deprecate Collection>>#sum altogether :)) > > Cheers, > Doru > > >> On Dec 30, 2015, at 12:53 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Hi Henrik, >> >>> On 25 Dec 2015, at 14:08, Henrik Nergaard <henrin10(a)student.uia.no> wrote: >>> >>> Like this? >>> http://smalltalkhub.com/#!/~Latsabben/NumIt >> >> That is a cool take on a possible approach. Thanks for doing it, it makes it much easier to think about and discuss alternatives. >> >> This inspired me to do something similar, but not quite. I am just thinking out loud by implementation. Here is my result: >> >> <Collections-Operations-SvenVanCaekenberghe.1.mcz> >> >> There are some examples in the class comments. >> >> Sven >> >>> Best regards, >>> Henrik >>> >>> -----Original Message----- >>> From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of stepharo >>> Sent: Thursday, December 24, 2015 9:58 AM >>> To: Pharo Development List <pharo-dev(a)lists.pharo.org> >>> Subject: Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers: >>> >>> Just a remark. >>> I think that we discarded the proposition of having >>> >>> aCol arithmetic sum >>> >>> but I found it nice because there if was clear that you want to get back >>> 0 for #(). >>> >>> Stef >>> >> > > -- > www.tudorgirba.com > www.feenk.com > > "Innovation comes in the least expected form. > That is, if it is expected, it already happened." > >

Jan. 7, 2016

ifError: implementation is bad

by Denis Kudriashov

Hi I look at implementation of BlockClosure>>ifError: . I did't know that it culls arguments to errorBlock. But what is this arguments? It is not error instance but specific properties from it. BlockClosure>>ifError: errorHandlerBlock ^ self on: Error do: [:ex | errorHandlerBlock cull: ex description cull: ex receiver] Why people doing that? Many users of it just pass given error like [...] ifError: [:msg :rcv | ... rcv error: msg]. Especially it is commonly used scenario by senders of #critical:ifError:. But it is different question. I propose change ifError: to cull error instance. What you think? Can be put it in Pharo 5? Such change can touch some packages

Jan. 7, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50515 Home: https://github.com/pharo-project/pharo-core

Jan. 7, 2016

[pharo-project/pharo-core] 1e5f02: 50515

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 1e5f02fb1c6562967d4bfd842a0685f4a2093208 https://github.com/pharo-project/pharo-core/commit/1e5f02fb1c6562967d4bfd84… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-01-07 (Thu, 07 Jan 2016) Changed paths: M BaselineOfQualityAssistant.package/BaselineOfQualityAssistant.class/instance/api projectSpec/baseline_.st M ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/symbolic versions/development_.st M ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/symbolic versions/stable_.st R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/pre2%5F2%5F0_.st A ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/pre2%5F3%5F0_.st A ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F2%5F0_.st A Kernel-Tests.package/MutexTest.class/README.md A Kernel-Tests.package/MutexTest.class/definition.st A Kernel-Tests.package/MutexTest.class/instance/helpers/fork_.st A Kernel-Tests.package/MutexTest.class/instance/helpers/fork_at_.st A Kernel-Tests.package/MutexTest.class/instance/running/setUp.st A Kernel-Tests.package/MutexTest.class/instance/running/tearDown.st A Kernel-Tests.package/MutexTest.class/instance/tests/testExecutionCriticalSection.st A Kernel-Tests.package/MutexTest.class/instance/tests/testFailedCriticalSectionShouldUnblockWaitingOne.st A Kernel-Tests.package/MutexTest.class/instance/tests/testTerminatedCriticalSectionShouldUnblockWaitingOne.st A Kernel-Tests.package/MutexTest.class/instance/tests/testTerminatingBlockedCriticalSectionShouldNotUnblockAnotherWaitingSection.st A Kernel-Tests.package/MutexTest.class/instance/tests/testTerminatingBlockedCriticalWhichWasSignalledButNotResumedYet.st A Kernel-Tests.package/MutexTest.class/instance/tests/testTwoCriticalsShouldWaitEachOther.st A Kernel-Tests.package/MutexTest.class/instance/tests/testTwoRecursiveCriticalsShouldNotWaitEachOther.st M QualityAssistant.package/QANautilusPluginMorph.class/instance/list-morph/getCritics.st M QualityAssistant.package/QANautilusPluginMorph.class/instance/task handling/excecuteTask.st M QualityAssistant.package/QANautilusPluginMorph.class/instance/task handling/taskCompleted.st A QualityAssistant.package/extension/CompiledMethod/instance/glmSourcePresentationIn_.st M QualityAssistant.package/extension/ReAbstractCritic/instance/gtInspectorSourceCodeIn_.st A QualityAssistant.package/extension/TBehavior/instance/glmSourcePresentationIn_.st A QualityAssistantRecording.package/QAEventCollector.class/README.md A QualityAssistantRecording.package/QAEventCollector.class/class/accessing/uniqueInstance.st A QualityAssistantRecording.package/QAEventCollector.class/class/class initialization/initialize.st A QualityAssistantRecording.package/QAEventCollector.class/class/initialize-release/unload.st A QualityAssistantRecording.package/QAEventCollector.class/definition.st A QualityAssistantRecording.package/QAEventCollector.class/instance/events/recordAnnouncement_.st A QualityAssistantRecording.package/QAEventCollector.class/instance/initialization/initialize.st A QualityAssistantRecording.package/QARCriticAutofixedEvent.class/README.md A QualityAssistantRecording.package/QARCriticAutofixedEvent.class/definition.st A QualityAssistantRecording.package/QARCriticBannedEvent.class/README.md A QualityAssistantRecording.package/QARCriticBannedEvent.class/definition.st A QualityAssistantRecording.package/QARCriticBannedEvent.class/instance/accessing/entityBanLevel.st A QualityAssistantRecording.package/QARCriticBannedEvent.class/instance/initialization/fromAnnouncement_.st A QualityAssistantRecording.package/QARCriticEvent.class/README.md A QualityAssistantRecording.package/QARCriticEvent.class/class/initialization/fromAnnouncement_.st A QualityAssistantRecording.package/QARCriticEvent.class/definition.st A QualityAssistantRecording.package/QARCriticEvent.class/instance/accessing/entity.st A QualityAssistantRecording.package/QARCriticEvent.class/instance/accessing/timestamp.st A QualityAssistantRecording.package/QARCriticEvent.class/instance/initialization/fromAnnouncement_.st A QualityAssistantRecording.package/QARCriticEvent.class/instance/initialization/initialize.st A QualityAssistantRecording.package/QARCriticsSeenEvent.class/README.md A QualityAssistantRecording.package/QARCriticsSeenEvent.class/definition.st A QualityAssistantRecording.package/QAREntityCriticizedEvent.class/README.md A QualityAssistantRecording.package/QAREntityCriticizedEvent.class/definition.st A QualityAssistantRecording.package/QARInitiateCriticBanEvent.class/README.md A QualityAssistantRecording.package/QARInitiateCriticBanEvent.class/definition.st A QualityAssistantRecording.package/QARMultipleCriticsEvent.class/README.md A QualityAssistantRecording.package/QARMultipleCriticsEvent.class/definition.st A QualityAssistantRecording.package/QARMultipleCriticsEvent.class/instance/accessing/critics.st A QualityAssistantRecording.package/QARMultipleCriticsEvent.class/instance/initialization/fromAnnouncement_.st A QualityAssistantRecording.package/QARSingleCriticEvent.class/README.md A QualityAssistantRecording.package/QARSingleCriticEvent.class/definition.st A QualityAssistantRecording.package/QARSingleCriticEvent.class/instance/accessing/critic.st A QualityAssistantRecording.package/QARSingleCriticEvent.class/instance/initialization/fromAnnouncement_.st A QualityAssistantRecording.package/QARViewedDiffEvent.class/README.md A QualityAssistantRecording.package/QARViewedDiffEvent.class/definition.st A QualityAssistantRecording.package/extension/ClassDescription/instance/asCollectedRingDefinition.st A QualityAssistantRecording.package/extension/CompiledMethod/instance/asCollectedRingDefinition.st A QualityAssistantRecording.package/extension/QACriticsSeen/instance/asQAREvent.st A QualityAssistantRecording.package/extension/QAInitiateCriticBan/instance/asQAREvent.st A QualityAssistantRecording.package/extension/QAViewedDiff/instance/asQAREvent.st A QualityAssistantRecording.package/extension/RPackage/instance/asCollectedRingDefinition.st A QualityAssistantRecording.package/extension/ReCriticAutofixed/instance/asQAREvent.st A QualityAssistantRecording.package/extension/ReCriticBanned/instance/asQAREvent.st A QualityAssistantRecording.package/extension/ReEntityCriticized/instance/asQAREvent.st A QualityAssistantRecording.package/extension/TraitDescription/instance/asCollectedRingDefinition.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50514.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50515.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50514.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50515.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50515 17329 Mutex should has tests https://pharo.fogbugz.com/f/cases/17329 17210 QualityAssistant v2.2.0 https://pharo.fogbugz.com/f/cases/17210 http://files.pharo.org/image/50/50515.zip

Jan. 7, 2016

Re: [Pharo-dev] ConfigurationOfXXX package is not visible in nautilus...

by Dimitris Chloupis

yes i can confirm this too, for IconFactory, this is definitely a bug On Thu, Jan 7, 2016 at 12:34 PM Skip Lentz <skip.lentz(a)inria.fr> wrote: > I loaded a configuration too (not with command line), and it wasnât in the > Configurations group. > > The spotter finds it, and auto-completion does too. It canât be found in > Nautilus.. > > On Jan 7, 2016, at 11:29 AM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > > is in Configurations group :) > thatâs by design, I think > > On 07 Jan 2016, at 11:14, Blondeau Vincent <vincent.blondeau(a)worldline.com> > wrote: > > Hi, > > Happy new year ! > > It seems that any configuration loaded by Jenkins is not visible in > Nautilus (at package level) but are accessible via the Spotter (at class > level). Does someone know why? > > I opened a bug: > https://pharo.fogbugz.com/f/cases/17342/Configuration-OfXXX-packages-are-no… > > > Thanks in advance, > > Vincent > > > ------------------------------ > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage > exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret > professionnel. Si vous recevez ce message par erreur, merci d'en avertir > immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne > pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra > Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs > efforts soient faits pour maintenir cette transmission exempte de tout > virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa > responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un > virus transmis. > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this > e-mail in error, please notify the sender immediately and destroy it. As > its integrity cannot be secured on the Internet, the Worldline liability > cannot be triggered for the message content. Although the sender endeavours > to maintain a computer virus-free network, the sender does not warrant that > this transmission is virus-free and will not be liable for any damages > resulting from any virus transmitted. > > > >

Jan. 7, 2016

Re: [Pharo-dev] ConfigurationOfXXX package is not visible in nautilus...

by Stephan Eggermont

On 07-01-16 11:14, Blondeau Vincent wrote: > It seems that any configuration loaded by Jenkins is not visible in > Nautilus (at package level) but are accessible via the Spotter (at class > level). Does someone know why? I have recently seen that error, but couldn't reproduce it. Stephan

Jan. 7, 2016

Re: [Pharo-dev] ConfigurationOfXXX package is not visible in nautilus...

by Skip Lentz

I loaded a configuration too (not with command line), and it wasnât in the Configurations group. The spotter finds it, and auto-completion does too. It canât be found in Nautilus.. > On Jan 7, 2016, at 11:29 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > is in Configurations group :) > thatâs by design, I think > >> On 07 Jan 2016, at 11:14, Blondeau Vincent <vincent.blondeau(a)worldline.com <mailto:vincent.blondeau@worldline.com>> wrote: >> >> Hi, >> >> Happy new year ! >> >> It seems that any configuration loaded by Jenkins is not visible in Nautilus (at package level) but are accessible via the Spotter (at class level). Does someone know why? >> >> I opened a bug: https://pharo.fogbugz.com/f/cases/17342/Configuration-OfXXX-packages-are-no… <https://pharo.fogbugz.com/f/cases/17342/Configuration-OfXXX-packages-are-no…> >> >> Thanks in advance, >> >> Vincent >> >> >> >> Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. >> >> This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. >

Jan. 7, 2016