(AKA Perverse Perlish Notation)
See the specs for it (half-hearted documentation) at
my web site -- note: Netscape seems to feel my CSS isn't worthy of being rendered, while MSIE and Mozilla find it just fine.
Expect a parser within a week. It's actually far easier to parse RPN than it is regular Perl, since nested things become flat (like the Earth):
$foo{bar}[ blat(\%foo) ] = { a => 'fool' };
is represented in RPN as:
foo$ bar {} foo%\ blat [] (a => 'fool') {} =;
# or, if you feel better binding things a little closer...
foo$ bar{} (foo%\ blat)[] (a => 'fool'){} =;
Oh, note that:
foo$ x$[] # $foo[$x]
is COMPLETELY different from:
foo$ x$[] = # $foo = [$x]
But the parser will know how to differentiate, due to syntax rules:
# what is:
foo$ x$[] y$[] =;
# is it...
$foo[$x] = [$y];
# or...
$foo = [$x][$y];
# it can't be the second (since that's a syntax error)
japhy --
Perl and Regex Hacker
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.