Some wise words of wisdom from Elian on whether to build code into a module ... :-)

  1. If you're going to do something more than twice, make it a function
  2. If you're going to use it in more than two programs, make it a module
  3. If doing it even once made your head hurt, throw it in a module
  4. If it has data you don't want to change yourself, make it work from template files
  5. If the code is could be generated from some sort of parameters, use a templating code generator for it
  6. If it feels like a monkey could do it, check the above list to see what you missed

 

perl -le 'print+unpack("N",pack("B32","00000000000000000000001000111110"))'

In reply to Re: Should I Make A Module? by rob_au
in thread Should I Make A Module? by coolmichael

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.