Re: A Peeve of Great Pettishness
What should this module do, if anything?
What special side effects should it have? Special variables? Special functions?
My thinking is that it should be largely useless, somewhat curious, marginally helpful (but perhaps not helpful enough to justify using it) and occasionally annoying.
Unless someone can give me a better idea...
Perhaps it should be Blovinator::Purple ?? Nah, that's too rational. If I need another color, it only makes perverse sense to do Purple::Blovinator::Green (for example).
But, it really shouldn't be at the top level, should it? It should be subordinated into an existing top-level package, don't you think? Especially since it's value-free.
package Purple::Blovinator;
use 5.008003;
use strict;
use warnings;
require Exporter;
our @ISA = qw(Exporter);
our @EXPORT_OK = qw( toString );
our $VERSION = '1.00';
{
sub toString { __PACKAGE__ }
sub new { return bless {}, shift }
# ...
}
1;
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.