Re: yaml last update

From: "Kent S." <ksibilev@...>
Date: 2004-05-15 20:25:54 UTC
List: ruby-core #2877
Another problem:

$ irb
irb(main):001:0> require 'yaml'
=> true
irb(main):002:0> class A
irb(main):003:1> attr_accessor :text
irb(main):004:1> end
=> nil
irb(main):005:0> a = A.new
=> #<A:0x60cc3c>
irb(main):006:0> a.text =<<EOS
irb(main):007:0" line 1
irb(main):008:0" line 2
irb(main):009:0" EOS
=> "line 1\nline 2\n"
irb(main):010:0> YAML.load(a.to_yaml)
ArgumentError: parse error on line 6, col -1: `'
         from /usr/local/lib/ruby/1.9/yaml.rb:30:in `load'
         from /usr/local/lib/ruby/1.9/yaml.rb:30:in `load'
         from (irb):10
irb(main):011:0> a.to_yaml
=> "--- !ruby/object:A \ntext: >\nline 1\n\nline 2\n\n"
irb(main):012:0>


Cheers,
Kent.

On May 15, 2004, at 4:07 PM, Kent S. wrote:

> It seems that the last yaml update broke ri system:
>
> $ ri local
> /usr/local/lib/ruby/1.9/yaml.rb:158:in `instance_variable_set': 
> `@Time.local( year [, month, day, hour, min, sec, usec] ) => time 
> (NameError)
> Time.local( sec, min, hour, day, month, year, wday, yday, isdst,
> tz ) => time
> Time.mktime( year, month, day, hour, min, sec, usec )   => time
>
> visibility' is not allowed as an instance variable name from 
> /usr/local/lib/ruby/1.9/yaml.rb:158:in `object_maker'
>         from /usr/local/lib/ruby/1.9/yaml.rb:157:in `each_pair'
>         from /usr/local/lib/ruby/1.9/yaml.rb:157:in `object_maker'
>         from /usr/local/lib/ruby/1.9/yaml/rubytypes.rb:36
>         from /usr/local/lib/ruby/1.9/yaml/rubytypes.rb:34:in `call'
>         from /usr/local/bin/ri:16:in `transfer'
>         from /usr/local/lib/ruby/1.9/yaml.rb:30:in `load'
>         from /usr/local/lib/ruby/1.9/yaml.rb:30:in `load'
>          ... 6 levels...
>         from /usr/local/lib/ruby/1.9/rdoc/ri/ri_driver.rb:122:in 
> `process_args'
>         from /usr/local/lib/ruby/1.9/rdoc/ri/ri_driver.rb:121:in `each'
>         from /usr/local/lib/ruby/1.9/rdoc/ri/ri_driver.rb:121:in 
> `process_args'
>         from /usr/local/bin/ri:21
>
>
> Cheers,
> Kent.
>
>


In This Thread