. I like the idea of allowing both OO and non-OO,

So do I. The problem is that at a pedantic level the implementation is broken. CGI's more so than OOorNo, but.....

Just document the inflexibility of the code,

Neither CGI or OOorNo document the weaknesses of their approach. Reading the source is required to figure out what is wrong, and frankly in both cases Id guess that a fair amount of experience is required to spot the weaknesses.

IMO part of a computer programmers job is to think about how things can be broken. CGI makes attempts in that direction OOorNo does not. Neither are satisfactory on an abstract level.

--- demerphq
my friends call me, usually because I'm late....

In reply to Re: Re: Re: Re: Handy dandy CPAN pollution by demerphq
in thread Handy dandy CPAN pollution by Juerd

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.