I think this node is probably dead now but...

Thanks to all that replied. I appreciate a laugh even if it's at my own expense :-)

In an effort to improve my code I have:
* Removed all printing to a log file (I never look at it)
* Removed redundant lines of code (where I could identify them

I also intend to:
* Set variables to 0 or is that '' or NULL after they've been used - ie where I read in the log file on the client machine
* Look at my use of loops to see if it could be simplified
* Think about using STRICT (I know I should but I am lazy)
* Post my code (in a much better formatted way) next time I ask a dumb question.

One final question - Is what I'm describing a memory leak, or should I have said "Excessive use of memory"

Thanks to one and all.


In reply to Re: Memory Leak Advice by 2mths
in thread Memory Leak Advice by 2mths

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.