The problem is that
- we do not want to open alone another subproject
- we would like to remove the old stream (make them loadable)
- we should not get the system with two stream libraries.
Stef
Le 23/3/15 10:06, Denis Kudriashov a écrit :
2015-03-23 0:40 GMT+03:00 stepharo <[email protected]
<mailto:[email protected]>>:
Le 22/3/15 22:05, Sven Van Caekenberghe a écrit :
On 22 Mar 2015, at 21:44, Denis Kudriashov
<[email protected] <mailto:[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
I was reading the XTreams API recently but this is forbidden for
me to open another project before finishing
what I started. Now if somebody else would like to help pushing
Xtreams in Pharo 50.
I think it is important to have XStreams in pharo by default. Because
current streams (from Smalltalk 80) are too powerfull. And when
XStreams not in image or can't be loaded easilly people can prefer to
use existed streams solution. I was such man when I was need quickly
solve some parsing and analizing data task but I can't load XStreams.
And I was solve my task with classic streams. It was simple solution.
But with XStreams it will be much compact and intuitive implementation.
