On Nov 22, 6:40 pm, "J. Clifford Dyer" <[EMAIL PROTECTED]> wrote:
> You yourself said that performance is a complaint of yours regarding Ruby, so > why claim that Ruby's way is clearly better in a case where it causes a known > performance hit? See Hrvoje's remark above -- we can have EOF and eat it too! Perhaps it was just somehow omitted from the standard Python library because it disliked by some folks or just forgotten. Is there a history of the eof()'s fall from grace? Was it ever considered for inclusion? Cheers, Alexy -- http://mail.python.org/mailman/listinfo/python-list