[#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: uninit bug in yaml/emitter.c

From: Yukihiro Matsumoto <matz@...>
Date: 2006-05-03 17:27:04 UTC
List: ruby-core #7816
Hi,

In message "Re: uninit bug in yaml/emitter.c"
    on Wed, 3 May 2006 11:20:13 +0900, "Pat Eyler" <rubypate@gmail.com> writes:

|During our hacking night, we also looked at an UNINIT bug in yaml/emitter.c
|It looked like that actual problem was in syck_scan_scalar.   We think the
|following is the right way to fix things, but would appreciate someone looking
|at it and committing if appropriate.

I think you're write.  I will merge the patch.  I hope _why could
follow up his copy of the syck repository.

							matz.

In This Thread