It may not be idiomatic; or as concise; or as efficient; but there is no reason it cannot be readable.
It's just bigger, more lines of code. More characters in line. More scrolling needed.
this
if ($x && $s =~ /(abc|def)/)
is more readable than this
if ($x && index($s, "abc") >= 0 || index($s, "def") >= 0)
It is also a really strange claim. I mean, decently formatted C code is perfectly readable.
Good C code is readable. But good perl code more readable than good C code.
Do you perchance mean "isn't considered readable" by YOU?
Of course. Should I append "IMHO" to every my posting?
And if you are unfamiliar with Perl idioms; it is probably far more readable to you than idiomatic Perl.
And if you are familar only with Assembler idioms, Assembler is more readable than Perl, and even more, than C
without citing the source of authority
cpan grep for index
-
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>
<u> <ul>
-
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
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
