[#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: [ ruby-Bugs-4457 ] Strange interactions between Struct and 'pp'

From: Tom Copeland <tom@...>
Date: 2006-05-18 20:52:45 UTC
List: ruby-core #7907
On Sat, 2006-05-13 at 16:39 +0900, Tanaka Akira wrote:
> In article <200605121513.k4CFDWsl029144@rubyforge.org>,
>   noreply@rubyforge.org writes:
> 
> >> ruby -rpp -e 'pp Struct.new(:members).new'
> > /usr/lib/ruby/1.8/pp.rb:181:in `__send__': undefined method `each' for nil:NilClass (NoMethodError)
> 
> Thank you for the report.
> 
> I fixed the problem.

I also received an additional note from Gustav Munkby, who reported the
bug.  He asked me to post it here:

================
It might however also be nice to document explicitly for the
Struct class that the built-in methods are overridden by the
accessor functions. If I use a Struct this is clearly what I
would expect, but to prevent others that want to iterate
over the Struct members for instance to perform the same
mistake.
================

Yours,

Tom




In This Thread

Prev Next