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

[BUG] round trip failure with YAML; both ruby_1_8 and HEAD

From: Mauricio Fernandez <mfp@...>
Date: 2006-05-31 15:25:26 UTC
List: ruby-core #7934
I caught syck corrupting data once again, and traced it down to this:

$ cat yamlbug.rb 
require 'yaml'

orig = "\n"
new = YAML.load(YAML.dump(orig))
puts "Should be #{orig.inspect}, but is: #{new.inspect}"
puts "YAML: #{YAML.dump(orig).inspect}"

$ ruby -v yamlbug.rb 
ruby 1.8.4 (2006-05-18) [i686-linux]
Should be "\n", but is: ""
YAML: "--- |\n\n\n"

$ ruby19 -v yamlbug.rb 
ruby 1.9.0 (2006-05-18) [i686-linux]
Should be "\n", but is: ""
YAML: "--- |\n\n\n"


It's a bit unreassuring.

-- 
Mauricio Fernandez  -   http://eigenclass.org   -  singular Ruby

In This Thread

Prev Next