Re: socket.c - s_recvfrom

Yukihiro Matsumoto wrote:
> Hi,
> 
> In message "Re: socket.c - s_recvfrom"
>     on Thu, 7 Jul 2005 12:24:50 +0900, Zach Dennis <[e-mail]> writes:
> 
> |If I am reading s_recvfrom correctly in can throw an error which kills 
> |the application...
> |
> |Would it make sense for it to return a -1 if the underlying call to 
> |recvfrom failed, like the unix system call recvfrom does?
> 
> No, every system call in Ruby throw an exception on failure
> consistently.  If I change the recvfrom behavior, it causes a bad
> inconsistency.  Can you accustom yourself to the Ruby Style? 

I figured you'd have a good reason. I am trying to wrap my head around 
some of the underlying c implementation, and i happened to to have been 
working with sockets quite a bit in these past few days.

This may be a little off, but socket documentation is not so good right 
now. I would even try to write some of the socket documentation myself 
if I could submit it to someone with understanding to check it for 
correctness, and perhaps add to it for completeness if i miss anything.

Zach