Why do you say that the input is creating what you're expecting? The in.yaml you give above produces:
{ arguments => [{ value => "test" }], options => [ { param => "i", value => 1001 }, { param => "f" }, { param => "x", value => "eyes" }, ], path => "/export/home/frank", }

IE. the top level items (arguments,options,path) are in a hash, which is an unordered set in Perl. You've lost your ordering on input, not on output. Unless you're talking about the options? In which case both formats are equivalent, at least to the YAML::XS loader which creates the same data structures in both cases.

In what external context does the yaml produced by YAML::XS cause a problem? Because both formats generate the same data structures in Perl and therefore should be interchangeable without issue.


In reply to Re^3: Keeping Order with YAML::XS by Loops
in thread Keeping Order with YAML::XS by walkingthecow

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.