Perl Monk, Perl Meditation | |
PerlMonks |
Re: Re: Re: Re: Re: Method Calls on multiple objectsby dragonchild (Archbishop) |
on Mar 27, 2004 at 21:50 UTC ( [id://340307]=note: print w/replies, xml ) | Need Help?? |
If an aggregate served a purpose beyond simple aggregation, that's one thing. But, to create an aggregate class simply to collect things ... that's the red flag. We already have something that collects things - an array. Unless you're spicing up the array somehow, there's no reason to create an additional syntax just to be more OO.
Some reasons I could think for creating an aggregate class:
Remember - we don't want to go the Smalltalk/Java route where you have a Collection, SortedCollection, Set, Bag, etc. Or, the C++ version where each of those are templated to comply with strong typing. Leverage what exists - don't reinvent the wheel. ------
Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose
In Section
Seekers of Perl Wisdom
|
|