comment on

UPDATE: Problem solved with YAML-0.39

Hi, up to now, I often used YAML to make data dumps, because it gave a nicely indented printout. But I just ran into a situation where YAML drops data on it's printout, but Data::Dumper dosn't. What I am doing is converting a 1 meg xml file to a user-friendly-hash and dumping the hash.

Here is a damaged portion of the YAML dump, the keys begin with SH, followed by a sub hash. I've commented where the YAML dump fails, it truncates the previous key's "stop" and "writer" subhash, and the next key is truncated to ':'. Data::Dumper will not make this error.

Has anyone seen this sort of thing before?

......
......
      SH563415.0000:   
        actors: ''
        category: 'Children Series '
        channel: 99
        channel_info: 9 CBET fcc CBET
        description: ''
        director: ''
        episode_num: SH563415.0000
        length: ''
        makedate: ''
        rating: ''
        star_rating: ''
        start: 09:45
    :           # key lost, as well as previous key's stop and writer
        actors: ''
        category: 'Children Animated Series '
        channel: 99
        channel_info: 9 CBET fcc CBET
        description: A canine's adventures when he was very young.
        director: ''
        episode_num: SH596834.0000
        length: ''
        makedate: ''
        rating: ''
        star_rating: ''
        start: 08:00
        stop: 08:30
        writer: ''
      SH608927.0000:    #beginning of next key
......
......
[download]

I'm not really a human, but I play one on earth. flash japh

In reply to Is YAML reliable on big files? by zentara

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


There's more than one way to do things
	PerlMonks