I'm working on a project that has quite a few classes already and is likely to grow significantly. I have been using Class::Accessor to generate my accessor methods. I selected it initially because it's simple; as were my needs. The only thing I dislike about Class::Accessor is that the default constructor requires arguments to be passed in as a hashref rather than the more usual (and slightly more efficient) list of key => value pairs.

Anyway, I'm planning to start using mixins. I've done this before simply by using multiple inheritance (MI). The Spiffy docs say:

if you've done much MI you've probably run into weird problems and headaches

I can't say I've suffered that yet, but if a) I'm likely to and b) Spiffy can help, then it might be worth a look.

The first thing that struck me as odd about Spiffy was the talk of exporting. I'd generally considered OO modules and exporting to be mutually exclusive. That may be a narrow minded view so feel free to expand my mind:-)

It's now occurred to me that I might want to override print in one of my classes. Then I realised that the override would not be inherited by a derived class and suddenly I wondered if exporting might not be such a bad idea after all.

Has Spiffy changed your life? Do tell.

PS: If you like Spiffy, you might want to rate it - no one has yet.