ode in jirb, the call blocks
> > at read, as expected. I also made a script of this, and run it with
> > jruby, and it seems to block. which means I cannot reproduce this
> > behaviour.
> >
> > Regards
> > Ola Bini
> >
> > - Original Message -
t; - Original Message -
> From: Evan <[EMAIL PROTECTED]>
> Date: Friday, April 7, 2006 10:00 pm
> Subject: [Jruby-devel] 0.8.3 Socket implementation broken
> To: [email protected]
>
>> I'm porting my socket+send/recv patch to w
TED]>
Date: Friday, April 7, 2006 10:00 pm
Subject: [Jruby-devel] 0.8.3 Socket implementation broken
To: [email protected]
> I'm porting my socket+send/recv patch to work with jruby 0.8.3 but
> thereseems to be a bug in the vanilla jruby 0.8.3 socket
> implemen
ed"-line at all?
Regards
Ola Bini
- Original Message -
From: Evan <[EMAIL PROTECTED]>
Date: Friday, April 7, 2006 10:00 pm
Subject: [Jruby-devel] 0.8.3 Socket implementation broken
To: [email protected]
> I'm porting my socket+send/recv patch to work
I'm porting my socket+send/recv patch to work with jruby 0.8.3 but there
seems to be a bug in the vanilla jruby 0.8.3 socket implementation.
"read" (I haven't tried write...) returns something (instead of blocking)
which when accessed crashes the interpreter. Since the IO code seems to
have chang
