[#7055] More on VC++ 2005 — Austin Ziegler <halostatue@...>

Okay. I've got Ruby compiling. I'm attempting to get everything in

17 messages 2006/01/05
[#7058] Re: More on VC++ 2005 — nobuyoshi nakada <nobuyoshi.nakada@...> 2006/01/06

Hi,

[#7084] mathn: ugly warnings — hadmut@... (Hadmut Danisch)

Hi,

22 messages 2006/01/10
[#7097] Re: mathn: ugly warnings — Daniel Berger <Daniel.Berger@...> 2006/01/10

Hadmut Danisch wrote:

[#7098] Design contracts and refactoring (was Re: mathn: ugly warnings) — mathew <meta@...> 2006/01/10

Daniel Berger wrote:

[#7118] Re: Design contracts and refactoring (was Re: mathn: ugly warnings) — mathew <meta@...> 2006/01/12

*Dean Wampler *<deanwampler gmail.com> writes:

[#7226] Fwd: Re: Question about massive API changes — "Sean E. Russell" <ser@...>

Hello,

23 messages 2006/01/28
[#7228] Re: Question about massive API changes — Caleb Tennis <caleb@...> 2006/01/28

>

Re: YAML.load({[]=>""}.to_yaml)

From: "H.Yamamoto" <ocean@...2.ccsnet.ne.jp>
Date: 2006-01-15 14:43:27 UTC
List: ruby-core #7159
Hi.

>>> After changing test script a bit, ("self.send m" => "self.funcall m") looks working.
>>
>>with GC.stress = true ?
>>-- 
>>Tanaka Akira
>
>No, I didn't try it. But anway, 100 times was not enough. After increased it to million times,
>error was reported.

This is because YAML is not handling CR and LF properly.
By following change, test script passed 100_000 times.

def random_string
  len = rand(4)
  chars = []
  (0...len).each {|i|
    ## don't check bytes with MSB.
    #chars << rand(256)
    c = rand(128)
    chars << c if c != ?\r && c != ?\n # << workaround >>
  }
  chars.pack("C*")
end

1.8.1 treats escape seaquence as string, but 1.8.4 treats it as binary?

E:\ruby-cvs\win32>ruby -ryaml -e 'puts YAML.dump("\n")'
--- |

E:\ruby-cvs\win32>ruby -ryaml -e 'puts YAML.dump("\t")'
--- !binary |
CQ==

And I tried GC.stress, there seems not to be GC problem.

Umm, there is still problem, but I think empty seq/map problem was solved by my patch.
If there is no objection, I want to commit it tommorow or later.


In This Thread