ANSI is a standard and there are cases where it is wrong (commitee
decisions = compromise)
On Jun 5, 2008, at 3:27 PM, Bill Schwab wrote:
Lukas,
I have blind copied someone who can comment, or not at his discretion,
on Cincom's view on this; he never said he was commenting off the
record, but I try to err toward assuming that. I got the distinct
sense
that they are contemplating a change of some type and are also
struggling with backward compatibility.
You are correct about ANSI; I was shocked to see what they did.
Without reservation, I assert the standard is wrong. Exception
handling
was created to allow the widespread elimination of precisely the
condition that arises when #next reads off the end of a stream. I can
always (and probably will if we do not fix this) deprecate #next and
#next: in my own work, but that still leaves inconsistencies between
and
within dialects.
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] 6/5/2008 7:18 AM >>>
Yes, but it is not consistent, and they are apparently not happy
with it.
Why? Can you give any pointers?
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.
As far as I see this is inconsistent with the ANSI standard.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
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
