I am not complaining about these exchanges, which were interesting indeed.

Just that P7 is still in flux and not something I can use in some way for
my projects.

No problem with that, just that I cannot afford using it in projects for
clients, it is too much of a risk. So, I am not testing it as much as I'd
I have found that the real issues show up with cases I face in such


On Fri, Apr 13, 2018 at 11:39 AM, Alistair Grant <akgrant0...@gmail.com>

> On 13 April 2018 at 11:04, Sven Van Caekenberghe <s...@stfx.eu> wrote:
> >
> >
> >> On 13 Apr 2018, at 08:43, p...@highoctane.be wrote:
> >>
> >> I consider Pharo 7 as a great piece of kit but unusable for my current
> work. There are many new things to learn in there. When is too much too
> much? Also, simplifications are breaking things in unexpected ways (like
> the #atEnd thing).
> >
> > Phil,
> >
> > Nothing fundamental will break with #atEnd.
> >
> > What you are reading in pharo-dev is a constructive discussion that (for
> me at least) started with the desire to support one very special kind of
> stream (stdin in C terms), something 99.99% of Pharo users have never seen,
> used or heard of.
> Completely agree (despite one of my later messages to Sven being
> overly grumpy).  I've learnt a lot from this exchange.
> Cheers,
> Alistair
> > Zn streams have worked well and as expected for Pharo versions going
> back to 3, that won't change.

Reply via email to