|> I always start with `perldoc YAML'
That's what I did too, but the synopsis actually starts with YAML, not with Perl structures.
grinder and your technique is great for those who are good at thinking in, and writing, Perl data structures. I must shamefully confess that, despite long experience programming Perl, I have trouble distinguishing braces from brackets from curlies, and remembering which does what. So I thought to myself: "Hey, YAML, human-readable! Maybe it can save me from wearing out my AltGr key! (on French keyboard)". But YAML turned out not to be as DWIM as I expected, which isn't surprising. Hence the need for lots of examples for lazy newbies like me.
Maybe as penance (and when I have time, this was all supposed to be a timesaver...) I'll write up a translation of perldsc into YAML.
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.