>The author introduced a new root namespace: Handy::. This is a big
>mistake.

This isn't permanent. It is being changed, and rightly so. It was never meant to remain under that namespace. The bulk of the code present isn't going to remain in the module. The module isn't needed by File::Util anymore and won't remain among it's prerequisites -I just hadn't handled that yet. Further, the module isn't to remain on the CPAN when File::Util is updated (very soon) so that it doesn't use Handy::Dandy.


>He used OOorNo, which he also wrote himself. A useless module that gives you
>your arguments without the first one if that's a class or object.

Refer to CGI::self_or_default( )
How useful you find this routine is a matter of situational basis and opinion.


>This has nothing to do with object orientation,

That depends. It is named OOorNo is it not? This code is not to remain under it's current namespace either, and the module removed from CPAN.


>it's just some very strange and useless syntactic sugar: you can now use
>Package->function and $object->funtion instead of Package::function. Yay?


use Foo qw( bar baz );

Foo->bar(woot);

I don't think so.


>Documentation
>
>Yeah, good question. Where is it?

There's not much documentation since the module isn't going to stay there more than the few days it would be present to provide needed support for File::Util. I don't want to argue about whether this practice of code provision and retraction is correct. It's not. It won't happen again by me. I appologize.


>I see no reason to be nice to this author.  He polluted CPAN

I'm sorry. I'll clean up my mess.


>and didn't read perlfaqs, didn't read
>http://pause.perl.org/pause/query?ACTION=pause_04about

That's presumptuous.

"When you're done with all your preparations, considerations, and investigations, visit the PAUSE and fill in the form for a new module namespace. Take your time filling in the rationale of the module proposal. Consider, your form will be posted to modules@perl.org too, so other developers will probably stumble over this description many years later. The better the decription, the better the chances that your module will actually be used."
"You need not wait for approval. You can upload anytime, even before you fill in the form. Uploading and registering are only loosely coupled." -taken from http://pause.perl.org/pause/query?ACTION=pause_04about.

I don't know all the "unwritten" rules I guess. I'll keep my ears perked up and my eyes open for these.

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