At least the CPUs that I am familiar with, the Z80 and the x86, both had local variables in the stack, and I've used them to quite some extent in assembly language.
Personally, I believe you will be far better off by throwing your current 14-sub 3200-line script away and reimplement it as separate files. merlyn is always eager to offer code review, both public and private, and there is also the code review ladder mailing list, that also will do a Perl code review for you.
Go there, show them your code, and in the process of explaining the code to them, you will find valuable practices to keep and valuable changes to implement.
-
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.
|
