Why would you use a Collection class in Perl?

1. You want a type-independent way of handling bunches of things. (In Perl, substitute "class" for "type".)
2. You want to encapsulate your grouping functionality so that:
   1. Everyone in a large group does it the same way.
   2. You can change the functionality "under the hood" easily
3. You don't want to use tie because
   1. it's a P.O.S. that is annoying to maintain
   2. it doesn't scale well
   3. no-one but you understands completely
   4. it's aesthetically unpleasing when compared to your class hierarchies

People are going to object to a lot of what I just said, especially the "so everyone does it the same way" point. "What about TMTOWTDI?!" some might scream. Well, TMTOWTDI is great for your personal stuff. TMTOWTDI is great when you golfing.

TMTOWTDI is NOT great when you're working in a group of 15 people and attempting to make near-impossible deadlines. Under those conditions, you pick one way, prove that it works, then have everyone else use it. If it's encapsulated, all the better.

------
We are the carpenters and bricklayers of the Information Age.

Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.