You do realise that you are forcing perl to redefine your hash with every call to your sub don't you!!!! By moving the hash definition out of the sub this will run so many orders of magnitude faster it is not funny (roughly 50,000 lines per second in my testing on a mid range single processor PIII 1.2GHz server....) 

# first define our hash (just the once not for every bloody line!!!!!!
+ :o)
my %opcodes = ( blah );

open (SOURCE, "<z80code.s") or die "Couldn't open source file.";
open (DEST, ">z80code.o") or die "Couldn't open destination file.";
while (<SOURCE>)
{
    print DEST encode($_)."\n";
}


sub encode{

    # blah

}

[download]

cheers

tachyon

s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print

In reply to Re: Z80 Assembler -> Hex Opcode by tachyon
in thread Z80 Assembler -> Hex Opcode by Elgon

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.