From: loats205@... (loats205)
Date: 2003-05-12T09:17:27+09:00
Subject: Expected behavior in the socket library

I use ruby mostly for IO/Socket type stuff, and there seems to be an
inconsistency in the socket library, specifically the TCPSocket class. I just
recently moved from 1.7.2 Self Installing version to a recent stable snapshot.
In the 1.7.2 msnwin version, when you socket.gets from a socket with the read
stream closed, nil is returned, on the other hand, when you socket.gets in the
1.6.8 snapshot, Errno::EINVAL is raised, and in a few instances, a segfault
occurs. I guess what im asking is what the expected behavior is, and what
version of the mswin32 port actually exhibits it. thanks in advance.

Jesse