Broken YAML.dump with YAML::Object (Missing String#each)

Jonathan Gold

Guest

Posts: n/a

05-19-2009

I feel like I've discovered a bug in YAML.dump when used with
yaml-tagged objects (YAML::Object). It seems that the YAML libs are
still expecting to use String#each, but that's gone. To repro:

ruby -ryaml -e 'anon_obj_yaml = "---
!ruby/object:No::Such::Class"; anon_obj = YAML.load( anon_obj_yaml );
YAML.dump( anon_obj )'

Is this a bug?

jon

Thread Tools
Show Printable Version Email this Page

Posting Rules
You may not post new threads You may not post replies You may not post attachments You may not edit your posts BB code is On Smilies are On [IMG] code is On HTML code is Off Trackbacks are On Pingbacks are On Refbacks are Off Forum Rules

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Why are "broken iterators" broken?	Steven D'Aprano	Python	8	09-28-2008 09:19 PM
Re: Why are "broken iterators" broken?	Fredrik Lundh	Python	0	09-22-2008 04:32 PM
Re: Why are "broken iterators" broken?	Cameron Simpson	Python	0	09-22-2008 04:32 AM
Latest WIndows Update for Wireless-G PCI Adapter Broken?	Paul Moloney	Wireless Networking	0	06-13-2005 06:40 PM
wireless broken	Nasir Sadi	Wireless Networking	0	03-16-2005 04:13 PM