[#7872] Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...>

All, I needed a nonblocking socket connect for my asynchronous-event

18 messages 2006/05/14
[#7873] Re: Nonblocking socket-connect — Tanaka Akira <akr@...17n.org> 2006/05/14

In article <3a94cf510605140559l7baa0205le341dac4f47d424b@mail.gmail.com>,

[#7874] Re: Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...> 2006/05/15

How about introducing the method Socket#set_nonblocking, or alternatively

[#7875] Re: Nonblocking socket-connect — Yukihiro Matsumoto <matz@...> 2006/05/15

Hi,

[#7876] Re: Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...> 2006/05/15

Well, it's ok then. I'm comfortable adding in the nonblocking

[#7877] Re: Nonblocking socket-connect — Yukihiro Matsumoto <matz@...> 2006/05/15

Hi,

Re: Coverity: Patch/Fix CID 17 OVERRUN_STATIC File: ruby/signal.c

From: Yukihiro Matsumoto <matz@...>
Date: 2006-05-05 15:41:23 UTC
List: ruby-core #7825
Hi,

In message "Re: Coverity: Patch/Fix CID 17 OVERRUN_STATIC File: ruby/signal.c"
    on Fri, 5 May 2006 11:28:23 +0900, Kevin Tew <tewk@tewk.com> writes:

|This is a simple out of bounds array access error.
|The error checking code is off by 1.  > Should be >=.
|Comments and suggestions welcome.
|If there are no objections, could someone commit the fix.

I did.  Thank you.

							matz.

In This Thread

Prev Next