Hi,

On 10/1/05, akira yamada / やまだあきら <akira / ruby-lang.org> wrote:
>
> I received a report from a Debian user:
> <URL:http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=331050>
>
> In Ruby 1.8.2:
>
>   $ ruby -v
>   ruby 1.8.2 (2005-04-11) [i386-linux]
>   $ ruby -ryaml -e 'puts YAML.dump(1234567890)'
>   --- 1234567890
>   $ ruby -ryaml -e 'puts YAML.dump(1234567890)' | ruby -ryaml -e 'p YAML.load(ARGF.read)'
>   1234567890
>
> In Ruby 1.8.3 (and trunk):
>
>   $ ruby -v
>   ruby 1.8.3 (2005-09-21) [i486-linux]
>   $ ruby -ryaml -e 'puts YAML.dump(1234567890)'
>   !ruby/object:Bignum 1234567890
>   $ ruby -ryaml -e 'puts YAML.dump(1234567890)' | ruby -ryaml -e 'p YAML.load(ARGF.read)'
>   /usr/lib/ruby/1.8/yaml.rb:133:in `transfer': allocator undefined for Bignum (TypeError)
>           from /usr/lib/ruby/1.8/yaml.rb:133:in `load'
>           from -e:1
>
> It is a bug of Ruby 1.8.3.  I think that YAML should be able to load
> "!ruby/object:Bignum 1234567890".
>

I did receive very similar reports from users of Alexandria
(http://alexandria.rubyforge.org/).  Seemed to work with 1.8.2 but not
anymore with 1.8.3.  Definitely looks like a regression.

cheers

Laurent