You should document it so a competent Perl programmer can understand it and then leave a copy of O'Reilly's Learning Perl. Your supervisor isn't going to be the one patching your project - he doesn't know perl. If he *is* doing that then I know where to find one supervisor that is wasting his time. Your documentation may include pictures, strategy documents, revision histories or whatever else is needed to encapsulate the higher-level order to the application. Lower level things should be documented inline unless you think it's important enough to document separately.
There's no magic here - an $Language programmer is required to work with $Language programs.
-
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.
|