This is not tested.

my $reader = YAML::ReadStream( $file_handle ); while ( my $document = $reader->() ) { ... } sub YAML::ReadStream { my $handle = shift; my $buffer; return sub { if ( eof $handle ) { undef $buffer; return undef; } else { return YAML::_ReadOneDocument( $handle, \ $buffer ); } }; } sub YAML::_ReadOneDocument { my $handle = shift; my $buffer = shift; while ( 1 ) { if ( eof $handle ) { return YAML::Load( $$buffer ); } read $handle, $$buffer, 8192, length $$buffer; my $yaml_header_position = index $$buffer, "\n---", length( "- +--" ); if ( $yaml_header_position >= 0 ) { my $doc = substr $$buffer, 0, $yaml_header_position, ''; return YAML::Load( $doc ); } } }

In reply to Re: YAML: reading a file w/ multiple docs in it, doc by doc by diotalevi
in thread YAML: reading a file w/ multiple docs in it, doc by doc by water

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.