in reply to How Many Modules Is Too Many?
It's an interesting question, and it is 'academic' because there is an infinite supply of problems to solve. Enough is never enough. I get that attitude as a C coder where there is an ocean of existing code, but it is far more work gluing it together, and you have to really understand it almost as as much as if you wrote it sometimes. Perl takes modularity to the next level. Maybe it makes it too easy? I occasionally think I have a useful module candidate, but I rarely wrap it up and publish because when I look there are two or three existing ones. The time when
enough definitely is enough is when there are too many very similar things. Even with Perls great handling of versions and
the awesome CPAN it's easily possible to load a bunch of deprecated old modules with overlapping functionality unless you look very closely at what you're requiring. But then you should do that anyway.
In the context of the Perl Quiz, which looks very interesting btw, you might want to look at the rules viz modules, they may differ from the comments here. For the current puzzle (hangman) I think you could probably crack it with a one liner for style points.
|