February 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] #valueWithPossibleArgs:, #valueWithEnoughArguments:, and #cull:

by Stefan Marr

Ah, sorry, yes #valueWithArguments: does throw errors. Best regards Stefan > On 19 Feb 2018, at 20:17, Stefan Marr <smalltalk(a)stefan-marr.de> wrote: > > Hi Mariano: > >> On 19 Feb 2018, at 20:09, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >> >> I guess it's because we offer both flavors. If you see valueWithArguments: you will see it does throw errors like #value* / #cull* do. > > Did you try my examples? > I donât think this is correct. > In Pharo 6.1, #valueWithArguments: doesnât throw any errors as far as I can see. It inserts nil for absent arguments however. > > This is what I tried: > > blocks := { > [ { } ]. > [:a | { a } ]. > [:a :b | { a. b } ]. > [:a :b :c | { a. b. c } ] > }. > > blocks collect: [:b | b valueWithPossibleArgs: {1}]. > blocks collect: [:b | b valueWithPossibleArgs: {1. 2. 3}]. > blocks collect: [:b | b valueWithEnoughArguments: {1}]. > blocks collect: [:b | b valueWithEnoughArguments: {1. 2. 3}]. > > > Best regards > Stefan > > > -- > Stefan Marr > School of Computing, University of Kent > http://stefan-marr.de/research/ > > -- Stefan Marr School of Computing, University of Kent http://stefan-marr.de/research/

Feb. 19, 2018

Re: [Pharo-dev] #valueWithPossibleArgs:, #valueWithEnoughArguments:, and #cull:

by Stefan Marr

Hi Mariano: > On 19 Feb 2018, at 20:09, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > I guess it's because we offer both flavors. If you see valueWithArguments: you will see it does throw errors like #value* / #cull* do. Did you try my examples? I donât think this is correct. In Pharo 6.1, #valueWithArguments: doesnât throw any errors as far as I can see. It inserts nil for absent arguments however. This is what I tried: blocks := { [ { } ]. [:a | { a } ]. [:a :b | { a. b } ]. [:a :b :c | { a. b. c } ] }. blocks collect: [:b | b valueWithPossibleArgs: {1}]. blocks collect: [:b | b valueWithPossibleArgs: {1. 2. 3}]. blocks collect: [:b | b valueWithEnoughArguments: {1}]. blocks collect: [:b | b valueWithEnoughArguments: {1. 2. 3}]. Best regards Stefan -- Stefan Marr School of Computing, University of Kent http://stefan-marr.de/research/

Feb. 19, 2018

Re: [Pharo-dev] #valueWithPossibleArgs:, #valueWithEnoughArguments:, and #cull:

by Mariano Martinez Peck

On Fri, Feb 16, 2018 at 2:25 PM, Stefan Marr <smalltalk(a)stefan-marr.de> wrote: > Hi: > > I am trying to understand the different between and perhaps origin of > BlockClosure>>#valueWithPossibleArgs: and BlockClosure>># > valueWithEnoughArguments: > > I am trying to decide which of the two I need for SOMns. > > The first one has seen more recent changes, when looking at the Pharo 6.1 > download: > > valueWithPossibleArgs: anArray â> 2/12/2017 StephaneDucasse > valueWithEnoughArguments: anArray â> 3/11/2001 nk > > While they have rather different implementations, they seem to behave > identically, as far as I could tell using the following example: > > blocks := { > [ { } ]. > [:a | { a } ]. > [:a :b | { a. b } ]. > [:a :b :c | { a. b. c } ] > }. > > blocks collect: [:b | b valueWithPossibleArgs: {1}]. > blocks collect: [:b | b valueWithPossibleArgs: {1. 2. 3}]. > blocks collect: [:b | b valueWithEnoughArguments: {1}]. > blocks collect: [:b | b valueWithEnoughArguments: {1. 2. 3}]. > > I was also wondering how they relate to #cull:* > > One of the major differences seems to be that valueWithP* and valueWithE* > are both injecting nil for absent arguments, while normal #value* and > #cull* methods signal an error. > Is there a specific use case why one wouldnât want to be strict here as > well, but instead inject nils? > I guess it's because we offer both flavors. If you see valueWithArguments: you will see it does throw errors like #value* / #cull* do. > Any comments or pointer appreciated. > > Thanks > Stefan > > > -- > Stefan Marr > School of Computing, University of Kent > http://stefan-marr.de/research/ > > > > -- Mariano http://marianopeck.wordpress.com

Feb. 19, 2018

[ANN] ba-st Web Stack new versions available

by Gabriel Cotelli

Hi, We're happy to announce a new version of the Web Stack hosted at https://github.com/ba-st/. This is a multi-release announcement of the following related project versions: - Willow <https://github.com/ba-st/Willow> v6.0.0. Changes since latest announcement: - Added interaction on document load - Improved temporarily disabling command - Added identification support to unordered lists - Improved new location opening commands - Improved interaction fuctions to always include the event as a parameter - Improved asynchronic links to auto-configure a script doing preventDefault - Refactored the link support - Willow-Bootstrap <https://github.com/ba-st/Willow-Bootstrap> v6.0.0 - Updated Willow base support to v6.0.0 - Improved Split Button support to allow triggering actions on the main button only - Willow-JQueryUI <https://github.com/ba-st/Willow-JQueryUI> v5.0.0 - Updated Willow base support to v6.0.0 - Willow-SpinKit <https://github.com/ba-st/Willow-SpinKit> v3.0.0 - Updated Willow base support to v6.0.0 - Willow-Playground <https://github.com/ba-st/Willow-Playground/> v2.0.0 - Updated dependencies to the latest versions - RenoirSt <https://github.com/ba-st/RenoirSt> v4.0.0 - Removed Pharo 4 support - Updated dependencies SemanticUI <https://github.com/ba-st/Willow-SemanticUI> integration is still a work in progress. There's a new Materialize CSS <https://github.com/fortizpenaloza/Willow-Materialize> integration being worked on by Francisco Ortiz. Find a more detailed changelog and migration instructions on the release pages of each repository. Anyone interested in joining our ba-st projects <https://github.com/ba-st/> is welcomed, and you can also start following our new tech blog @ mercap <https://medium.com/mercap-tech-blog> for Smalltalk and Pharo related posts and experience reports. Regards, Gabriel Cotelli, Maxi Tabacman and all the contributors.

Feb. 19, 2018

[Pharo 7.0-dev] Build #578: 21373-Fix-Tests-Failing-after-Change-in-Examples

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #578 was: SUCCESS. The Pull Request #916 was integrated: "21373-Fix-Tests-Failing-after-Change-in-Examples" Pull request url: https://github.com/pharo-project/pharo/pull/916 Issue Url: https://pharo.fogbugz.com/f/cases/21373 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 19, 2018

Re: [Pharo-dev] Iceberg 0.6.8 backported to 6.1

by Sean P. DeNigris

Sean P. DeNigris wrote > FYI #60530 is supposed to have Iceberg 0.6.8, but there is something > amiss. Any progress on this? I'm a bit stuck because I already started porting my baselines to use `gitlab://` ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 19, 2018

Re: [Pharo-dev] #valueWithPossibleArgs:, #valueWithEnoughArguments:, and #cull:

by Stefan Marr

Hi Clement: Thanks for looking into this! > On 19 Feb 2018, at 11:43, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > they're both very old. My guess is that there are two for compatibility purpose Ok, good to know. Thanks. > All use-cases of these methods I have found do not inject nils, they expect the block to have a number of arguments of the block less or equal to the number of parameters in the argument array. I would say theyâre used as #cullWithArguments: but for some reason other selector names were preferred. > [...] > There a few use-cases for nil injection though. Typically when changing existing frameworks in multiple repositories, it may be that during the update process the change to the caller is installed before the change of the callee, and if the code is actually used (code in UI for instance), injecting nils might avoid system break-down. Another use-case is for compatibility with frameworks using the nil injection, but I canât find a framework doing that right now. Ok, great. In the end, I only added #cullArguments: instead of the #valueWith* variants [1]. The naming seems to communicate more clearly the expected semantics, and itâs different from the previous ones. So, in case it turns out someone needs those with nil injecting semantics, they could be added later. Thanks Stefan [1] https://github.com/smarr/SOMns/pull/215/files#diff-8dd7efb0aab92cd4b39e0bf8… -- Stefan Marr School of Computing, University of Kent http://stefan-marr.de/research/

Feb. 19, 2018

[Pharo 7.0-dev] Build #577: 20481-all-methods-starting-with-example-should-also-have-a-sampleInstance-annotation

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #577 was: SUCCESS. The Pull Request #747 was integrated: "20481-all-methods-starting-with-example-should-also-have-a-sampleInstance-annotation" Pull request url: https://github.com/pharo-project/pharo/pull/747 Issue Url: https://pharo.fogbugz.com/f/cases/20481 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 19, 2018

[Pharo 7.0-dev] Build #576: 21371-Monticello-Tests-is-not-loaded-in-the-bootstraped-image

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #576 was: SUCCESS. The Pull Request #915 was integrated: "21371-Monticello-Tests-is-not-loaded-in-the-bootstraped-image" Pull request url: https://github.com/pharo-project/pharo/pull/915 Issue Url: https://pharo.fogbugz.com/f/cases/21371 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 19, 2018

Re: [Pharo-dev] [Pharo 7.0-dev] Build #574: 21226-GLMMorphicText-sents-unknown-secondClock

by Marcus Denker

> On 19 Feb 2018, at 12:23, ci-pharo-ci-jenkins2(a)inria.fr wrote: > > There is a new Pharo build available! > > The status of the build #574 was: FAILURE. > > The Pull Request #912 was integrated: "21226-GLMMorphicText-sents-unknown-secondClock" > Pull request url: https://github.com/pharo-project/pharo/pull/912 > > Issue Url: https://pharo.fogbugz.com/f/cases/21226 > Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… Downloading the latest pharoVM: http://files.pharo.org/get-files/70/pharo-linux-stable.zip mkdir: cannot create directory âpharo-vmâ: File exists I really wonder why it does that *sometimes*, but in most cases it works? => we should do the workaround: https://pharo.fogbugz.com/f/cases/21255/Zeroconf-script-should-re-use-exist… This will not fix the real reason, but I think is would be a good thing in general to make the zeroconf scripts just update existing downloads. Marcus

Feb. 19, 2018