A bit more testing reveals that this seems to be a problem of the mswin
version:

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\WINNT>ruby --version
ruby 1.6.7 (2002-03-01) [i586-mswin32]

C:\WINNT>ruby c:\temp\x.rb
6
17
<<hangs here>>


Linux:

knoppix@ttyp0[knoppix]$ uname -a
Linux Knoppix 2.4.19-rc3-xfs #1 SMP Die Jul 23 21:13:33 CEST 2002 i686
unknown unknown GNU/Linux
knoppix@ttyp0[knoppix]$ ruby --version
ruby 1.6.7 (2002-03-19) [i386-linux]
knoppix@ttyp0[knoppix]$ ruby /mnt/hda1/temp/x.rb
6
17
21
9
26
read: <<start
>>
30
knoppix@ttyp0[knoppix]$

I noticed also, that closing STDERR or $stderr does seem to close STDOUT,
too.  Is this intended behavior or is it a known bug?

    robert


"ts" <decoux / moulon.inra.fr> schrieb im Newsbeitrag
news:200305071636.h47GaiX26877 / moulon.inra.fr...
> >>>>> "C" == Carlos  <angus / quovadis.com.ar> writes:
>
> C> Doesn't hang here...
>
>  same doesn't hang
>
> C> Maybe you need to improve your ruby by 0.0.1 ;)
>
>  no, no, work fine with 1.6.7
>
>
> Guy Decoux
>
>