- Pharo-users - lists.pharo.org

Re: [Pharo-users] Set Rounding mode for IEEE floating point operations

by Steffen MÃ¤rcker

Yes, I was considering this in the context of some approximation algorithms. Maybe one of the VM experts here could comment on the possibility to implement that? Am .01.2018, 10:00 Uhr, schrieb Serge Stinckwich <serge.stinckwich(a)gmail.com>: > On Mon, Jan 15, 2018 at 12:27 PM, Steffen MÃ¤rcker <merkste(a)web.de> wrote: > >> Hi, >> >> is there any way to set the rounding mode for IEEE floating point >> operations? Maybe something like >> >> Double roundToMinusInfWhile: [... code goes here ...]Double >>> roundToZeroWhile: [... more code here ...] >>> >> >> If not, is it possible to add this behavior, e.g., via a custom >> primitive? >> >> > âThis might interesting to have something like that for PolyMath, but > I'm a > little worried of subtle consequences > that might appear in UI if you use points for examples.â

Jan. 22, 2018

Re: [Pharo-users] looking for another iterator :)

by Steffen MÃ¤rcker

Hi! this is straightforward with Transducers, e.g., > (Take n: 5) <~ #(1 2 3 4 5 6 7 8). or > #(1 2 3 4 5 6 7 8) transduce take: 5. The different primitives like take, drop, map, filter, etc. are composable and do not generate intermediate representations. The bad news are, that the Pharo port is incomplete and I won't have the time until April to finish it. Best, Steffen Am .01.2018, 10:57 Uhr, schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > 5

Jan. 22, 2018

Re: [Pharo-users] looking for another iterator :)

by Sven Van Caekenberghe

yes, we need composition to avoid API explosion (things are already very bad in this respect) > On 22 Jan 2018, at 10:38, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > In most collection libraries I know there is the "take" function coming from the functional world that does that: > > #(1 2 3 4 5 6 7 8) take: 5 > => #(1 2 3 4 5) > > #(1 2 3 4) take: 5 > => #(1 2 3 4) > > Now, I understand there are two different things in here. > - First is the fact that we would like to apply this iterator to more than sequenceable collections. I think that the name "take" is order agnostic in that sense. > - The other thing is that people would like to not calculate the sub-collection... The problem is that we will end up with ugly combinations of selectors like > > take:thenDo: > take:thenCollect: > take:thenSelect: > ... > > And that pattern already exists also for: > > select:thenCollect: > select:thenDo: > > collect:as: > select:as: > > ... > > I think I would like to have a more composable kind of iterators/collections. There are Transducers that make "iterators" kind of command objects that you can apply on a collection. Personally I don't like the API choice but the idea behind is nice: > > https://github.com/Pharophile/Transducers > > sum := #+ init: 0. > sum1 := #(1 1 1) reduce: sum. > sum2 := (1 to: 1000) transduce: #odd filter reduce: sum. > > > And there are XTreams that allows one to work on a collection as a stream and then compose decorators on top. This means however that we need to create a stream and "close" it to obtain the resulting collection on every manipulation. > > https://github.com/mkobetic/Xtreams > https://code.google.com/archive/p/xtreams/wikis/Core.wiki > > ((aCollection reading collect: [ ... ]) select: [ ... ]) rest. > > Guille > > On Mon, Jan 22, 2018 at 4:11 AM, Ben Coman <btc(a)openinworld.com> wrote: > On 22 January 2018 at 00:47, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi Ben and Clement > > > > I have a collection (a dictionary in my case) and I want to get > > maximum 5 bindings out of it and iterate on them. > > I want keysAndValuesDo: or do: but only up to 5 elements. > > > > aDict atMax: 5 do: [:each | ] > > "atMax" sound a bit like comparison rather than counting. Perhaps > better would be... > aDict atMost: 5 do: [:each | ] "or" > aDict for: 5 do: [:each | ] > > but rather than introduce three or more messages... > aDict atMost: 5 do: [:each| ... ] > aDict atMost: 5 select: [:each| ... ] > aDict atMost: 5 collect: [:each| ... ] > > why not introduce just one method?.... > (aDict any: 5) do: [:each| ... ] > (aDict any: 5) select: [:each| ... ] > (aDict any: 5) collect: [:each| ... ] > > > cheers -ben > > > > So I learned from:to:do: > > > > aCollection atMax: 5 do: [:each | ] > > > > Does it make sense? > > > > Stef > > > > On Sun, Jan 21, 2018 at 1:16 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > >> I don't think we do. Do you need it on SequenceableCollection or > >> HashedCollection too ? > >> > >> Recently I was trying to iterate over the first N elements of a collection > >> and since there was no #first:do: I used #from:to:do:. I guess you could use > >> that too: > >> > >> aCollection from: 1 to: (aCollection size min: 1000) do: aBlock > >> > >> Which guarantees you iterate at max over 1000 elements. But that API is > >> SequenceableCollection specific. > >> > >> On Sun, Jan 21, 2018 at 11:44 AM, Ben Coman <btc(a)openinworld.com> wrote: > >>> > >>> On 21 January 2018 at 18:36, Stephane Ducasse <stepharo.self(a)gmail.com> > >>> wrote: > >>> > Hi > >>> > > >>> > I would like to iterate at max on a certain amount of elements in a > >>> > collection. > >>> > And I was wondering if we have such iterator. > >>> > >>> I'm not clear what functionality your asking for. Could you present > >>> it as code & result if you assumed the iterator you want was > >>> available? > >>> > >>> cheers -ben > >>> > >> > >> > >> > >> -- > >> ClÃ©ment BÃ©ra > >> Pharo consortium engineer > >> https://clementbera.wordpress.com/ > >> BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq > > > > > > > -- > > Guille Polito > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > CRIStAL - UMR 9189 > French National Center for Scientific Research - http://www.cnrs.fr > > Web: http://guillep.github.io > Phone: +33 06 52 70 66 13

Jan. 22, 2018

Re: [Pharo-users] looking for another iterator :)

by Guillermo Polito

In most collection libraries I know there is the "take" function coming from the functional world that does that: #(1 2 3 4 5 6 7 8) take: 5 => #(1 2 3 4 5) #(1 2 3 4) take: 5 => #(1 2 3 4) Now, I understand there are two different things in here. - First is the fact that we would like to apply this iterator to more than sequenceable collections. I think that the name "take" is order agnostic in that sense. - The other thing is that people would like to not calculate the sub-collection... The problem is that we will end up with ugly combinations of selectors like take:thenDo: take:thenCollect: take:thenSelect: ... And that pattern already exists also for: select:thenCollect: select:thenDo: collect:as: select:as: ... I think I would like to have a more composable kind of iterators/collections. There are Transducers that make "iterators" kind of command objects that you can apply on a collection. Personally I don't like the API choice but the idea behind is nice: https://github.com/Pharophile/Transducers sum := #+ init: 0. sum1 := #(1 1 1) reduce: sum. sum2 := (1 to: 1000) transduce: #odd filter reduce: sum. And there are XTreams that allows one to work on a collection as a stream and then compose decorators on top. This means however that we need to create a stream and "close" it to obtain the resulting collection on every manipulation. https://github.com/mkobetic/Xtreams https://code.google.com/archive/p/xtreams/wikis/Core.wiki ((aCollection reading collect: [ ... ]) select: [ ... ]) rest. Guille On Mon, Jan 22, 2018 at 4:11 AM, Ben Coman <btc(a)openinworld.com> wrote: > On 22 January 2018 at 00:47, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > > Hi Ben and Clement > > > > I have a collection (a dictionary in my case) and I want to get > > maximum 5 bindings out of it and iterate on them. > > I want keysAndValuesDo: or do: but only up to 5 elements. > > > > aDict atMax: 5 do: [:each | ] > > "atMax" sound a bit like comparison rather than counting. Perhaps > better would be... > aDict atMost: 5 do: [:each | ] "or" > aDict for: 5 do: [:each | ] > > but rather than introduce three or more messages... > aDict atMost: 5 do: [:each| ... ] > aDict atMost: 5 select: [:each| ... ] > aDict atMost: 5 collect: [:each| ... ] > > why not introduce just one method?.... > (aDict any: 5) do: [:each| ... ] > (aDict any: 5) select: [:each| ... ] > (aDict any: 5) collect: [:each| ... ] > > > cheers -ben > > > > So I learned from:to:do: > > > > aCollection atMax: 5 do: [:each | ] > > > > Does it make sense? > > > > Stef > > > > On Sun, Jan 21, 2018 at 1:16 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> > wrote: > >> I don't think we do. Do you need it on SequenceableCollection or > >> HashedCollection too ? > >> > >> Recently I was trying to iterate over the first N elements of a > collection > >> and since there was no #first:do: I used #from:to:do:. I guess you > could use > >> that too: > >> > >> aCollection from: 1 to: (aCollection size min: 1000) do: aBlock > >> > >> Which guarantees you iterate at max over 1000 elements. But that API is > >> SequenceableCollection specific. > >> > >> On Sun, Jan 21, 2018 at 11:44 AM, Ben Coman <btc(a)openinworld.com> > wrote: > >>> > >>> On 21 January 2018 at 18:36, Stephane Ducasse <stepharo.self(a)gmail.com > > > >>> wrote: > >>> > Hi > >>> > > >>> > I would like to iterate at max on a certain amount of elements in a > >>> > collection. > >>> > And I was wondering if we have such iterator. > >>> > >>> I'm not clear what functionality your asking for. Could you present > >>> it as code & result if you assumed the iterator you want was > >>> available? > >>> > >>> cheers -ben > >>> > >> > >> > >> > >> -- > >> ClÃ©ment BÃ©ra > >> Pharo consortium engineer > >> https://clementbera.wordpress.com/ > >> BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq > > > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Jan. 22, 2018

[JOB] Engineer 1 year: Pharo IoT platform

by Marcus Denker

Inria RMoD are looking for a full-time engineer for helping with developing Pharo in the context of IoT. The focus of this job is "Pharo on embedded and mobile devices for the internet of things" With Pharo, we have developed over the last two years an interactive, remote development environment. It allows embedded, headless software running on typical raspberry pi class hardware to be developed and debugged in an interactive way. It allows programmers to explore and change running headless embedded programs from their desktop development machine. The next step will be to extend this infrastructure to cover the use case of industrial use: Deployment. We want to build a middle-ware to manage, authenticate and script deployed Pharo embedded installations. The engineer will help to develop the Pharo IoT infrastructure, especially with a focus on industrial use: â¢ Improve Pharo for a platform with an industrial focus. â¢ Work on a middleware to manage deployed Pharo instances. â¢ Realize two small demos: First, as an industrial IoT example, a demo deployed on 20+ devices. Demo 2: Pharo deployed on multiple mobile autonomous robots. â¢ Help with creating a website for PharoIOT. We are looking for a candidate with some prior experience with Pharo. In addition: â¢ Knowledge in Dynamic Languages (Pharo is a plus but not required) â¢ Experience with embedded development is a plus but not required â¢ English Work in a research lab, but no paper writing, no teaching, no administration. In addition: â¢ Centrally located (one hour from Paris, 1h20 from London, 35 min from Brussels) â¢ Try a lot of good beer (our office is just 10km from the border to Belgium) â¢ Program with Pharo all day! â¢ Lille is an active city but not expensive (lot of students...), centrally located with good connections by train to everywhere (including CDG and Brussels airports). â¢ Duration: 12 Month â¢ Starting date: As soon as possible (Spring 2018) â¢ Salary: 2600-3200 euros brut / month, depending on experience â¢ Explanation Salary: french brutto = money after social charges (and base health insurance) before income tax, which is max one month income payed yearly, depending on family situation (can be 0 for a family with kids) â¢ Location: Lille (no remote job possible)) More about â¢ Pharo: http://www.pharo.org â¢ PharoThings: https://github.com/pharo-iot/PharoThings â¢ INRIA RMOD: http://rmod.lille.inria.fr â¢ INRIA Lille: http://www.inria.fr/lille â¢ INRIA in General: http://www.inria.fr â¢ Lille: â¢ http://en.wikipedia.org/wiki/Lille â¢ http://wikitravel.org/en/Lille Do not hesitate to contact us for more information. Permanent Link to this call: https://rmod.inria.fr/web/blog/2017-10-20

Jan. 22, 2018

Re: [Pharo-users] looking for another iterator :)

by Ben Coman

On 22 January 2018 at 00:47, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi Ben and Clement > > I have a collection (a dictionary in my case) and I want to get > maximum 5 bindings out of it and iterate on them. > I want keysAndValuesDo: or do: but only up to 5 elements. > > aDict atMax: 5 do: [:each | ] "atMax" sound a bit like comparison rather than counting. Perhaps better would be... aDict atMost: 5 do: [:each | ] "or" aDict for: 5 do: [:each | ] but rather than introduce three or more messages... aDict atMost: 5 do: [:each| ... ] aDict atMost: 5 select: [:each| ... ] aDict atMost: 5 collect: [:each| ... ] why not introduce just one method?.... (aDict any: 5) do: [:each| ... ] (aDict any: 5) select: [:each| ... ] (aDict any: 5) collect: [:each| ... ] cheers -ben > So I learned from:to:do: > > aCollection atMax: 5 do: [:each | ] > > Does it make sense? > > Stef > > On Sun, Jan 21, 2018 at 1:16 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: >> I don't think we do. Do you need it on SequenceableCollection or >> HashedCollection too ? >> >> Recently I was trying to iterate over the first N elements of a collection >> and since there was no #first:do: I used #from:to:do:. I guess you could use >> that too: >> >> aCollection from: 1 to: (aCollection size min: 1000) do: aBlock >> >> Which guarantees you iterate at max over 1000 elements. But that API is >> SequenceableCollection specific. >> >> On Sun, Jan 21, 2018 at 11:44 AM, Ben Coman <btc(a)openinworld.com> wrote: >>> >>> On 21 January 2018 at 18:36, Stephane Ducasse <stepharo.self(a)gmail.com> >>> wrote: >>> > Hi >>> > >>> > I would like to iterate at max on a certain amount of elements in a >>> > collection. >>> > And I was wondering if we have such iterator. >>> >>> I'm not clear what functionality your asking for. Could you present >>> it as code & result if you assumed the iterator you want was >>> available? >>> >>> cheers -ben >>> >> >> >> >> -- >> ClÃ©ment BÃ©ra >> Pharo consortium engineer >> https://clementbera.wordpress.com/ >> BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq >

Jan. 22, 2018

Re: [Pharo-users] looking for another iterator :)

by Richard Sargent

SomeCollection every: 5 do: [:subset | subset collect: [:each | ...]] etc. If you want the first five only, return from the do: block. Possibly, #every: by itself answers an iterator / collection conforming instance. On Jan 21, 2018 14:47, "James Foster" <Smalltalk(a)jgfoster.net> wrote: > Since âatMax:â doesnât seem as clear to me, Iâd prefer âupToMax:â or > âwithMax:â or (especially) the following: > > upTo: anInteger timesDo: aBlock > upTo: anInteger timesSelect: aBlock > upTo: anInteger timesCollect: aBlock > > James Foster > > > On Jan 21, 2018, at 8:56 AM, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > > > > I thought about something like that... > > > > SequenceableCollection >> atMax: numberOfItems do: aBlock > > "Execute the iteration with at the maximum numberOfItems. If the > > receiver contains less than numberOfItems iterate them all." > > 1 to: (numberOfItems min: self size) do: [:index | aBlock value: > > (self at: index)] > > > > This is an abstraction that we need to treat some samples. > > > > Stef > > > > On Sun, Jan 21, 2018 at 5:47 PM, Stephane Ducasse > > <stepharo.self(a)gmail.com> wrote: > >> Hi Ben and Clement > >> > >> I have a collection (a dictionary in my case) and I want to get > >> maximum 5 bindings out of it and iterate on them. > >> I want keysAndValuesDo: or do: but only up to 5 elements. > >> > >> aDict atMax: 5 do: [:each | ] > >> > >> So I learned from:to:do: > >> > >> aCollection atMax: 5 do: [:each | ] > >> > >> Does it make sense? > >> > >> Stef > >> > >> On Sun, Jan 21, 2018 at 1:16 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> > wrote: > >>> I don't think we do. Do you need it on SequenceableCollection or > >>> HashedCollection too ? > >>> > >>> Recently I was trying to iterate over the first N elements of a > collection > >>> and since there was no #first:do: I used #from:to:do:. I guess you > could use > >>> that too: > >>> > >>> aCollection from: 1 to: (aCollection size min: 1000) do: aBlock > >>> > >>> Which guarantees you iterate at max over 1000 elements. But that API is > >>> SequenceableCollection specific. > >>> > >>> On Sun, Jan 21, 2018 at 11:44 AM, Ben Coman <btc(a)openinworld.com> > wrote: > >>>> > >>>> On 21 January 2018 at 18:36, Stephane Ducasse < > stepharo.self(a)gmail.com> > >>>> wrote: > >>>>> Hi > >>>>> > >>>>> I would like to iterate at max on a certain amount of elements in a > >>>>> collection. > >>>>> And I was wondering if we have such iterator. > >>>> > >>>> I'm not clear what functionality your asking for. Could you present > >>>> it as code & result if you assumed the iterator you want was > >>>> available? > >>>> > >>>> cheers -ben > >>>> > >>> > >>> > >>> > >>> -- > >>> ClÃ©ment BÃ©ra > >>> Pharo consortium engineer > >>> https://clementbera.wordpress.com/ > >>> BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq > > > > > > >

Jan. 22, 2018

Re: [Pharo-users] looking for another iterator :)

by James Foster

Since âatMax:â doesnât seem as clear to me, Iâd prefer âupToMax:â or âwithMax:â or (especially) the following: upTo: anInteger timesDo: aBlock upTo: anInteger timesSelect: aBlock upTo: anInteger timesCollect: aBlock James Foster > On Jan 21, 2018, at 8:56 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > I thought about something like that... > > SequenceableCollection >> atMax: numberOfItems do: aBlock > "Execute the iteration with at the maximum numberOfItems. If the > receiver contains less than numberOfItems iterate them all." > 1 to: (numberOfItems min: self size) do: [:index | aBlock value: > (self at: index)] > > This is an abstraction that we need to treat some samples. > > Stef > > On Sun, Jan 21, 2018 at 5:47 PM, Stephane Ducasse > <stepharo.self(a)gmail.com> wrote: >> Hi Ben and Clement >> >> I have a collection (a dictionary in my case) and I want to get >> maximum 5 bindings out of it and iterate on them. >> I want keysAndValuesDo: or do: but only up to 5 elements. >> >> aDict atMax: 5 do: [:each | ] >> >> So I learned from:to:do: >> >> aCollection atMax: 5 do: [:each | ] >> >> Does it make sense? >> >> Stef >> >> On Sun, Jan 21, 2018 at 1:16 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: >>> I don't think we do. Do you need it on SequenceableCollection or >>> HashedCollection too ? >>> >>> Recently I was trying to iterate over the first N elements of a collection >>> and since there was no #first:do: I used #from:to:do:. I guess you could use >>> that too: >>> >>> aCollection from: 1 to: (aCollection size min: 1000) do: aBlock >>> >>> Which guarantees you iterate at max over 1000 elements. But that API is >>> SequenceableCollection specific. >>> >>> On Sun, Jan 21, 2018 at 11:44 AM, Ben Coman <btc(a)openinworld.com> wrote: >>>> >>>> On 21 January 2018 at 18:36, Stephane Ducasse <stepharo.self(a)gmail.com> >>>> wrote: >>>>> Hi >>>>> >>>>> I would like to iterate at max on a certain amount of elements in a >>>>> collection. >>>>> And I was wondering if we have such iterator. >>>> >>>> I'm not clear what functionality your asking for. Could you present >>>> it as code & result if you assumed the iterator you want was >>>> available? >>>> >>>> cheers -ben >>>> >>> >>> >>> >>> -- >>> ClÃ©ment BÃ©ra >>> Pharo consortium engineer >>> https://clementbera.wordpress.com/ >>> BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq > >

Jan. 21, 2018

Re: [Pharo-users] [Moose-dev] feenk log

by Tudor Girba

Hi, > On Jan 21, 2018, at 10:37 PM, Ben Coman <btc(a)openInWorld.com> wrote: > > On 21 January 2018 at 23:55, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> Hi, >> >> There is a difference in performance. The Announcement is slower (about 2-3x slower). However, for 1M events the difference is measured in a 200-400ms, which is very small. > > So you mean each event <1ms difference? > btw, what is the biggest usage of events? I guess mouse movements? > How many such events typically in 1 second of movement? > How is performance on StackInterpreter VM? > I guess we should keep that performant for platforms lacking JIT like > iPads, etcâ¦ It depends on the scene. We are still looking into how to evaluate this. Thatâs why we still have both implementations around. >> The benefit of using Announcement is that we can reuse the tooling around Announcement, such as blogging and debugging. > > This looks really useful. Can you describe the difference between the > red and blue lines in the picture of the first link? Each event goes through two passes, like in JavaScript: - The first is called âcapturingâ (or filtering) and goes from the root to the leaf. This is to allow a parent to prevent a child to react to an event. - The second one is called âbubblingâ (or handling) and goes from the leaf to the root. This is to find the most specific element to handle the event. Cheers, Tudor > cheers -ben > >> >> Still, the way it is used in Bloc is different from the typical usage in that Bloc registers to all Events (which are Announcements) and then dispatches through them to specific Element method (like BlEventListener>>clickEvent:). Still the cool thing is that you also can still register from the outside to a specific event using a normal when:do:. >> >> We will write a piece of doc about it. >> >> Cheers, >> Tudor >> >> >>> On Jan 21, 2018, at 4:46 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> >>> this looks really cool. >>> For the event I remember the discussion with glenn about the difference and I forgot. >>> >>> Stef >>> >>>> On 21 Jan 2018, at 15:54, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> >>>> Hi, >>>> >>>> Here is an update of the work on Bloc and GT. As always, please do let us know what you think. >>>> >>>> Bloc: >>>> - Eventing saw a deep overhaul. They are now dispatched using the Announcements engine. The previous mechanism is still in place in order to help people compare the impact. In the process, we also cleaned the propagation of events, and we made them debuggable through inspector extensions: >>>> https://twitter.com/feenkcom/status/955086133519618048 >>>> https://twitter.com/feenkcom/status/946482609680539649 >>>> - Embedding Bloc elements in Morphic is even easier now: >>>> https://twitter.com/feenkcom/status/946676667002556416 >>>> - We continued the work towards an interactive creation of a graphical scene: >>>> https://twitter.com/feenkcom/status/948492946541858816 >>>> - Theme experiment >>>> >>>> GT: >>>> - The documentation of Mondrian is available when you download the code and can be viewed using GT Documenter: >>>> https://twitter.com/feenkcom/status/939394586115563520 >>>> - The Mondrian extensions of BlElement are now extracted in a more general package that enables Bloc elements to be used in graph scenes. >>>> >>>> Have fun, >>>> The feenk team >>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> www.feenk.com >>>> >>>> "Obvious things are difficult to teach." >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)list.inf.unibe.ch >>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>> >>> -------------------------------------------- >>> StÃ©phane Ducasse >>> http://stephane.ducasse.free.fr >>> http://www.synectique.eu / http://www.pharo.org >>> 03 59 35 87 52 >>> Assistant: Julie Jonas >>> FAX 03 59 57 78 50 >>> TEL 03 59 35 86 16 >>> S. Ducasse - Inria >>> 40, avenue Halley, >>> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >>> Villeneuve d'Ascq 59650 >>> France >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)list.inf.unibe.ch >>> https://www.list.inf.unibe.ch/listinfo/moose-dev >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Beauty is where we see it." >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.tudorgirba.com www.feenk.com "Every thing should have the right to be different."

Jan. 21, 2018

Re: [Pharo-users] looking for another iterator :)

by Ben Coman

On 22 January 2018 at 00:47, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi Ben and Clement > > I have a collection (a dictionary in my case) and I want to get > maximum 5 bindings out of it and iterate on them. > I want keysAndValuesDo: or do: but only up to 5 elements. > > aDict atMax: 5 do: [:each | ] > > So I learned from:to:do: > > aCollection atMax: 5 do: [:each | ] > > Does it make sense? Just some random thoughts. Perhaps something more generic... aDict doN: [ :each :n | aCollection add: each] while: [ :each :n | n <=5 ] For #select: & #collect: there is a distinction to make whether it is 5 elements processed or 5 elements returned. aDict select: [ :each | "do something" ] while: [ :iterator | iterator selectedCount <= 5 ]. "or..." [ :iterator | iterator processedCount <= 5 ]. "or..." [ :iterator | (iterator element ~= "breakElement") cheers -ben > Stef > > On Sun, Jan 21, 2018 at 1:16 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: >> I don't think we do. Do you need it on SequenceableCollection or >> HashedCollection too ? >> >> Recently I was trying to iterate over the first N elements of a collection >> and since there was no #first:do: I used #from:to:do:. I guess you could use >> that too: >> >> aCollection from: 1 to: (aCollection size min: 1000) do: aBlock >> >> Which guarantees you iterate at max over 1000 elements. But that API is >> SequenceableCollection specific. >> >> On Sun, Jan 21, 2018 at 11:44 AM, Ben Coman <btc(a)openinworld.com> wrote: >>> >>> On 21 January 2018 at 18:36, Stephane Ducasse <stepharo.self(a)gmail.com> >>> wrote: >>> > Hi >>> > >>> > I would like to iterate at max on a certain amount of elements in a >>> > collection. >>> > And I was wondering if we have such iterator. >>> >>> I'm not clear what functionality your asking for. Could you present >>> it as code & result if you assumed the iterator you want was >>> available? >>> >>> cheers -ben >>> >> >> >> >> -- >> ClÃ©ment BÃ©ra >> Pharo consortium engineer >> https://clementbera.wordpress.com/ >> BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq >

Jan. 21, 2018