One things I consider viataly important when writing code, make it readable. Something that are just as valuable in perl as any other language, if not more so given the oportunity to abuse perl.

Avoid side effects, ensure that each line has a specific purpose. Try to ensure that each line performs a single operation. This will save you hours in debugging and maintenence. Likes such as: 

return $v[0]->[$h].$h[!!$h].$and[!!($h&&($t||$u))].$v[!(1==$t&&($u+=10
+)&&($t=0))]->[$t].$format{'space'}.$v[0]->[$u];

[download]
Should be split into several lines. Why write the code to be so difficult to read?

All in all very clever code, VERY hard to read, consequently its worth is much reduced.
--

Zigster

In reply to Re: (Zigster) My Laptop talks to me. by zigster
in thread My Laptop talks to me. by frankus

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.