[#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: [BUG] round trip failure with YAML; both ruby_1_8 and HEAD

From: MenTaLguY <mental@...>
Date: 2006-05-31 16:48:10 UTC
List: ruby-core #7935
On Thu, 1 Jun 2006 00:25:26 +0900, Mauricio Fernandez <mfp@acm.org> wrote:
> I caught syck corrupting data once again, and traced it down to this:
 
> orig = "\n"
> new = YAML.load(YAML.dump(orig))
> puts "Should be #{orig.inspect}, but is: #{new.inspect}"
> puts "YAML: #{YAML.dump(orig).inspect}"

Another (different, I think) roundtripping failure related to collapsing newlines is:

 orig = "hoge\n\nhoge"
 def orig.to_yaml_style ; :fold ; end
 new = YAML.load(YAML.dump(orig))
 puts "Should be #{orig.inspect}, but is: #{new.inspect}"
 puts "YAML: #{YAML.dump(orig).inspect}"

Which yields:

 Should be "hoge\n\nhoge", but is: "hoge\nhoge"
 YAML: "--- >-\nhoge\n\nhoge\n"

It's present in ruby_1_8 as of last week, at least.

-mental


In This Thread

Prev Next