Well, it took three long and intensive days once I started, but I converted all of libraries to modules and changed all of my programs which used the libraries to use the new modules. The code is much better now. Next I will have to do the same for my other web sites.
As an update on where I am now as a coder, I think a couple of years ago I would not have been able to have done this in just three days--it would have taken me at least three weeks, maybe months. I would have tried, gotten confused, stopped, and started again several times before working it out. When I made the previous post on this topic (A Matter of Style in CGI) several years ago, I would not have been able to have changed my libraries and all over to modules. It would have been beyond my comprehension. So, thanks especially for this suggestion. It has helped me to test my skills doing something in Perl that I had never tried to do before, or even thought of doing.
-Spenser
That's Spenser, with an "s" like the detective.
-
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.
|
