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

[ ruby-Bugs-4344 ] :!~ not a symbol

From: noreply@...
Date: 2006-05-03 07:41:42 UTC
List: ruby-core #7813
Bugs item #4344, was opened at 2006-05-03 17:41
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=4344&group_id=426

Category: Core
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Doug Kearns (dkearns)
Assigned to: Nobody (None)
Summary: :!~ not a symbol

Initial Comment:
:!~ is not an instance of Symbol as :=~ is.

irb(main):001:0> :!~.class
SyntaxError: compile error
(irb):1: parse error, unexpected tNMATCH, expecting tSTRING_CONTENT or tSTRING_DBEG or tSTRING_DVAR or tSTRING_END
:!~.class
   ^
        from (irb):1

It might just be due to the fact that tNMatch is not included as part of the "op" symbol in parse.y

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=4344&group_id=426

In This Thread

Prev Next