in reply to When are packages the right design choice?

Let's just put it this way - if your application is more than 200-300 lines, you should have a really good reason not break out into packages.

Now, packages don't necessarily mean OO. They could be Exporter packages that simply contain a bunch of (related) subroutines and data structures. They could be full-fledged OO hierarchies. That's up to you. But, the package breakout isn't Perl or OO specific. It's good programming specific.

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

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

I shouldn't have to say this, but any code, unless otherwise stated, is untested

  • Comment on Re: When are packages the right design choice?

In Section Meditations