Well, here's your chance to apply them.

It's good to see that TOMMY++ asks what we think about it. It appears my post wasn't useless. However, I'm not into OO, and don't think procedural and OO interfaces should be mixed the way OOorNo does. But since it's documented now (that's the way to go, Tommy!), I'll read the documentation to find out how and when the module can be useful. Until then, I'm not able to say anything more about it than I did in my original post in this thread.

Who's going to do that? How will disputes be resolved? What gives one person the right to prevent another from sharing their code in an open forum like CPAN? If people can't be bothered to do QA on a module before using it, they deserve the consequences.

A voting or reviewing system on search.cpan.org would be great. Maybe a namespace should be introduced for new modules that haven't been reviewed yet.

I don't buy the "Gives perl a bad name" argument either. What's next? Trying to prevent them from using established protocols to distribute their code?

CPAN is one of Perl's strengths. Without CPAN, Perl wouldn't be half as useful as it is now. CPAN is not good because code is shared with it. It is good because good code is shared with it. 

- Yes, I reinvent wheels.
- Spam: Visit eurotraQ.

In reply to Re: Re: Re: Re: Handy dandy CPAN pollution by Juerd
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.