I take pride in my documentation. It's FAR better than anything in perldoc.com
umm...

From one of your recent posts

if I documented it properly ... I'd know what needs to be cleared and wouldn't need a global clear function, but I don't know if creating the necessary documentation would have been practical without anticipating the final form of the script...
Let's please be clear. The very reason you wrote your VarStructor hack was due to another badly written 3400 line program of yours ("LinkStructor") that:
  1. You don't have time to rewrite to a better standard
  2. You don't have time to properly document
Interestingly, you do have time to write endless defenses of your "unconventional" and lamentable coding style in this forum.

The most concerning thing in all this is that the LinkStructor program in question, you are intending to market for your own commercial gain. This, despite acknowledged security holes and bugs.

Please please listen to Monks who know better than you. Reading your response to posts is like walking continuously into a brick wall.

In reply to Re: Re: Re: Re: Re: Preferred output for development tool by Anonymous Monk
in thread Preferred output for development tool by Wassercrats

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.