Well, then I guess it's a bug since then it should probably emit a parser error.
But note that this works:
sub CLASS_DEFINITION:
ATTRIBUTES:
PRIVATE: pvt_at1 pvt_at2 pvt_at3
PROTECTED: ptc_at1 ptc_at2 ptc_at3
PUBLIC: pub_at1 pub_at2 pub_at3
METHODS:
PRIVATE: pvt_mt1 pvt_mt2 pvt_mt3
PROTECTED: ptc_mt1 ptc_mt2 ptc_mt3
PUBLIC: pub_mt1 pub_mt2 pub_mt3
;
code edited: missing ':'
It gets interpreted to a lot of attributes. And it spans multiple lines.
Just a side note, but I actually wrote code that handles this sort of attribute depiction and creates the accessors methods and such.
Somehow, yesterday this all seemed like a very good idea but today it seems like a brain-dead way to do things.
But I'm still curious about all of this. Should I report it as a bug or something like that?
acid06
perl -e "print pack('h*', 16369646), scalar reverse $="
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.