[#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,

patch for UNINIT error in array.c

From: "Pat Eyler" <rubypate@...>
Date: 2006-05-03 02:23:15 UTC
List: ruby-core #7810
Along with the unitialized beg, we found a len which doesn't appear to be
initialized anywhere either.  Instead of the couple of patches proposed in the
earlier thread, this one seems like a better choice.  Please take a look at
it and commit if appropriate.


diff -p -u -r1.186 array.c
--- array.c     12 Dec 2005 16:46:59 -0000      1.186
+++ array.c     3 May 2006 02:22:50 -0000
@@ -2102,6 +2102,8 @@ rb_ary_fill(int argc, VALUE *argv, VALUE
     long beg, end, len;
     VALUE *p, *pend;
     int block_p = Qfalse;
+    beg = 0;
+    len = 0;

     if (rb_block_given_p()) {
        block_p = Qtrue;


In This Thread

Prev Next