This looks quite orderly, since the only words you are using here are 'eval', 'statement' and 'expression'.
If you fill that with 'real code', the picture will get different, and the tiny ':' will get hard to spot at a glance.
In contrast, 'if-elsif-else' statements stand out and are thus better readable on larger constructs.
As for \& {}, that's an abuse of the coderef constructor and it will clutter up your symbol table.
<expression> ?
eval {
<statement>;
<statement>;
<statement>;
<expression> ?
eval {
<statement>;
<statement>;
<statement>;
}
:
eval {
<statement>;
<statement>;
<statement>;
};
}
:
eval {
<statement>;
<statement>;
<statement>;
<expression> ?
eval {
<statement>;
<statement>;
<statement>;
}
:
eval {
<statement>;
<statement>;
<statement>;
};
};
|
if (<expression>) {
<statement>;
<statement>;
<statement>;
if (<expression>) {
<statement>;
<statement>;
<statement>;
}
else {
<statement>;
<statement>;
<statement>;
}
}
else {
<statement>;
<statement>;
<statement>;
if (<expression>) {
<statement>;
<statement>;
<statement>;
}
else {
<statement>;
<statement>;
<statement>;
}
}
|
What do you do with your large ?: construct if you have by chance to insert a third condition (a.k.a elsif) statement? Which of both columns is better readable? Can you tell at a glance if there's a semicolon missing (or one that causes a syntax error) on a line in the left column?
--shmem
_($_=" "x(1<<5)."?\n".q·/)Oo. G°\ /
/\_¯/(q /
---------------------------- \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}
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.