I never said I recommend it, just that I don't highly recommend it. Yes, it is a rude thing to do. But the request was "I have created a new 20-25 methods to add to the MP3::Napster.pm module", "wihout modifying the parent". Seems like a pretty rude thing to want to do.
If one is going to be rude, one might as well be rude in a very simple way than in a complex way.
Note that it is "unrude" in that
- If you don't require the new module(s), then MP3::Napster is completely unaffected.
- Anything that MP3::Napster already inherits from takes precedence over these new module(s) because I used push and not unshift (and because I force MP3::Napster to be initialized before I do the push).
So I'm on the fence as to whether one should ever do what I wrote or what was originally asked for, but I don't understand why you would need to do that. I'd probably create a separate class that inherits from both MP3::Napster and these new modules.
-
tye
(but my friends call me "Tye")
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.