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
IIRC, one difference between #get and #next is that
get cannot return nil and will throw an Incomplete exception when EOF
next can return nil and might throws an Exception
Changing the meaning of an existing selector will cause many problems and
discussions. People will think they do not have to change anything and they
will be wrong.
superb inconsistencet
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.
:)
Well, it does/did load OK in Pharo 3 and probably will in 4 too.
https://ci.inria.fr/pharo-contribution/job/Xtreams/
Yes loading is just a part of the story :)
We should remove the old ones.
And we should revise the API because
I **hate ++, -=, +=
Yeah, but is not because it looks a bit like C++ that it is no longer
Smalltalk, these are still normal messages.
But yes, some API discussions are possible.
