I'd totally agree... if the module's function was, as a Unix command is, small and tightly contained. If I'm looking for a module to give me some FTP functions, you bet I'd want the module to reflect that in the title.
On the other hand, something that gets to be a large framework, that almost by definition is a collection of smaller items put together in a useful way to allow you to easily accomplish some bigger task, very often could be served well by giving it a name. By your rationale, is "Apache" a terrible name for a webserver? Would we be any better off were it called "Open Source HTTP Server"??
Anyway, not sure we really disagree -- perhaps you missed the context in which I made my initial remark (to the idea that the OP's module was becoming a framework rather than a small utility).
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||