Sig, One of the great things about Smalltalk is that we are seldom forced to do anything, and certainly not in this case. It is easy to define #readStream where appropriate, and IMHO Pharo should do so. Not only does it give cleaner code, it will help us insert Nile when the time comes, and we can simply add the missing methods. I submit that the problem is instead all of the external code that will still explicitly reference ReadStream. That is not a reason to not make the change, and I am hoping that a little leadership by example will cause the right thing to happen across the board. More challenging still are the inconsistencies in exhaustion behavior. Referring to my proposal on the wiki, I stand ready to help if we want to enforce EndOfStreamError on any "unauthorized" exhaustion, but I have my doubts that we will do so; Cincom considered and declined the proposal. I can also not afford to wait for the decision to be made and imlemented. For now, I am gradually moving my code toward #nextOne, #nextMany:, etc., which again can be done simply by adding new code. If Pharo adopts EndOfStreamError, I can easily change from my new protocol to the more generic messages. FWIW, one of the first things I did was define #readStream on various collections and collection classes. Dolphin (sorry to keep beating the drum, but it sets a wonderful example!) has had #readStream "everywhere" for a long time if not from its earliest days. Bill -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Igor Stasenko Sent: Thursday, September 03, 2009 10:42 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [ANN] the problem that not all classes define #readStream.. as far as i remember, i had some issues with it, and forced to use "ReadStream on:" instead 2009/9/3 Stéphane Ducasse <stephane.ducasse@inria.fr>:
- Issue 1144: Â Many occurrences of "ReadStream on: aCollection" which can be replaced with "aCollection readStream"
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project