2015-03-23 9:57 GMT+03:00 stepharo <[email protected]>: > Le 22/3/15 23:01, Sven Van Caekenberghe a écrit : > >> On 22 Mar 2015, at 22:40, stepharo <[email protected]> wrote: >>> >>> >>> >>> Le 22/3/15 22:05, Sven Van Caekenberghe a écrit : >>> >>>> On 22 Mar 2015, at 21:44, Denis Kudriashov <[email protected]> >>>>> wrote: >>>>> >>>>> Hi >>>>> >>>>> It is another perfect task for XStreams: >>>>> >>>>> r := #('a12' 'b12' 'a13' 'a14' 'c23' 'a16') reading selecting: [:each >>>>> | each first = $a]. >>>>> r get > a12 >>>>> r get > a13 >>>>> >>>> Beautiful ! >>>> >>> Yes but with >>> r next. >>> r next >>> >> The choice for different selector names was intentional, by design. To >> avoid confusion, because #next and #get are not 100% identical >> (semantically). This is an important point. >> > No I asked martin personally. This is the real reason. There were also > experimenting to offer an API closer to other language. > So that we have > r get. > r next: 4 >
But in original docs from https://code.google.com/p/xtreams there are only #get and #read: messages.
