I like the parens, actually. But then, I came to Perl
from Emacs lisp...
I really can't stand Perl that's been written by an
extreme died-in-the-wool C programmer. It's one thing
to slip in an occasional semicolon-laden for loop
(though I'm not fond of too many of them), but when every
hash is pretending to be a struct and every array is
traversed using an index and every simple pattern
match is done with a loop and substr and every
interpolation is done with sprintf, I want to
scream. Don't get me wrong, I like sprintf, when
I need leading zeros or something... I'm only
talking about the people who use it when simple
interpolation would do fine. People who write
Perl like that should be punished by forcing them
to read a thousand lines of code that does
absolutely everything with closures.
for(unpack("C*",'GGGG?GGGG?O__\?WccW?{GCw?Wcc{?Wcc~?Wcc{?~cc'
.'W?')){$j=$_-63;++$a;for$p(0..7){$h[$p][$a]=$j%2;$j/=2}}for$
p(0..7){for$a(1..45){$_=($h[$p-1][$a])?'#':' ';print}print$/}
-
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.
|