[#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: [BUG] segfault on Proc#call after setting a trace_func

From: Yukihiro Matsumoto <matz@...>
Date: 2006-05-20 06:20:27 UTC
List: ruby-core #7912
Hi,

In message "Re: [BUG] segfault on Proc#call after setting a trace_func"
    on Sat, 20 May 2006 00:56:16 +0900, nobu@ruby-lang.org writes:

|> That's it.  Thank you.  Here's the patch to fix this.
|
|what state is this patch?

Applied to the local copy of the repository.  Waiting to be
committed.

							matz.

In This Thread