When assigning the %amino_acid_conversion, you could use newlines to make the code a bit more readable

Completely agree. I'd go even further and put whitespace around the fat commas and with so many entries I would sort by either key or value to make it easier to spot misses/dupes/typos.

%amino_acid_conversion = (
    ALA => 'A',
    ARG => 'R',
    ASN => 'N',
    ASP => 'D',
    CYS => 'C',
    GLN => 'Q',
    GLU => 'E',
    GLY => 'G',
    HIS => 'H',
    ILE => 'I',
    LEU => 'L',
    LYS => 'K',
    MET => 'M',
    PHE => 'F',
    PRO => 'P',
    SER => 'S',
    THR => 'T',
    TRP => 'W',
    TYR => 'Y',
    VAL => 'V'
);

[download]

🦛

In reply to Re^2: Issues regarding for loops and recursion by hippo
in thread Issues regarding for loops and recursion by Nickmofoe

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.