no this is the point.
We are learning.
I propose to harvest the on: change and have a pln for end of stream
behavior
stef
On Jun 5, 2008, at 1:06 PM, Bill Schwab wrote:
Damien, Lukas, Stef,
Yes, but it is not consistent, and they are apparently not happy
with it. Object Arts' solution is consistent both with itself and
with yoga of structured exception handling. However, at this point,
it appears that you do not want to make the change, so I will stop
pressing.
Bill
Wilhelm K. Schwab, Ph.D.
University of Florida
Department of Anesthesiology
PO Box 100254
Gainesville, FL 32610-0254
Email: [EMAIL PROTECTED]
Tel: (352) 846-1285
FAX: (352) 392-7029
[EMAIL PROTECTED] 06/05/08 6:27 AM >>>
On Thu, Jun 5, 2008 at 12:01 PM, Lukas Renggli <[EMAIL PROTECTED]>
wrote:
No surprise, I would argue that we proceed, and would also
include a
rename of #next to #nextOrNil and #next: to #nextAvailable:. All
code in
the image at the time should work as before.
What would be the impact on code that is not in the image? Would all
external packages need to be adapted as well or would the current
semantics
be preserved?
I suggest to implement #next so that it throws an EndOfStream
notification. The default action would return nil, so no existing
code
needs to be changed. People that want to use exceptions capture the
notification.
That's what is in VW apparently.
--
Damien Cassou
Peter von der Ahé: «I'm beginning to see why Gilad wished us good
luck». (http://blogs.sun.com/ahe/entry/override_snafu)
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
