What is "diverse code"?
Well, it seems the fast majority of the code you write are OO modules (99% you said). I write OO classes. I write procedural modules. Small ones. Large ones. I also write applications. Throw away applications. Applications that will be reused. Mason pages. Code that's run from modperl. Code that's run from the command line. Code that's run from cron. Code that runs on 5.8.x. Code that runs on 5.12.x.
Different code has different requirements. Where I may use autodie for a run-once program, I'm less likely to have a need for autodie for a module that sits between a webapp and a database. Whatever you come up with nextgen (or anyone else with a similar module), even if it's ideal for some of the code I write, it cannot be ideal for the majority of the code I write.
As I said before, the only modules/pragmas that are used in most of my modules are 'use strict; use warnings; use 5.XXX;'. There's nothing else that I use often enough that I want it loaded by default.
| [reply] |
| [reply] |
As I said, I write diverse code. None of the modules you mention, a majority of my code needs it. And it's unlikely I would ever write a file that needs all the modules your nextgen provides (and the more you add, the less likely it will be). But "use"ing modules you don't need have a negative impact: more dependencies, more chance of bugs, longer load times, more memory usage. More reason to just list the modules/pragmas you use instead of using a set of modules someone else finds convenient. | [reply] |
