Class-ifying objects is fundamental notion in the O-O universe. But so is encapsulation. If your code is not going to be using multiples of these message objects often throughout (I wouldn't call 3 or 4 times 'often'), then going to the trouble of rigorously class-ifying your objects may not be a useful return on your investment. Yes, you could come up with an interface definition that helps you to better class-ify your code, but is it worth the trouble, really?
What you have done that is wholly appropriate is to encapsulate the behavior of your objects using an idiom that you've come up with. It shouldn't be too hard to maintain this at the current level of usage.
Should you decide that this message object should be mutated and ubiquitous, then you might want to consider developing more O-O type software. Till then, I'd let it slide.
Drew
Be careful what you wish for... (Mr. Limpet)
For where you treasure is there shall your heart be also (Christ)
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.