From: why the lucky stiff <ruby-talk@...>
Date: 2004-07-02T10:44:53+09:00
Subject: Re: YAML BUG

haldane wrote:
> My theory is that yaml keeps a track of objects, and only assigns them
> an id number if it sees the object for the second time (in emitter.c).
>  If it does this, it tries to go back and write that id where the
> object first occurred.  But if the 4k buffer has already been exceeded
> and flushed, then the id cannot be written, and the whole object is
> written out again.  Causing an infinite loop.

This is definitely the problem.

> This is a serious problem.  If my theory is right, I guess it could be
> fixed by always writing an id for every object in the expectation that
> it may be met again?

This solution would make for a lot of ugly YAML.  Too big of a tradeoff 
for the lesser case of large recursive elements.

I'll just collect IDs for all the collections in a tree before emitting. 
  Ok, it's etched into the schedule.  Thank you!

_why