Re^2: Module Bloat and the Best Solution

If there's a bug, it can be corrected and you don't have to do anything.

Bugs won't fix themselves. If you find a bug in, say, XML::Twig, you're extremely lucky, because mirod really cares about his modules. How many CPAN authors are as responsive as he is?

If you you find a bug in a module whose author either doesn't care or has no time, then the bug is yours.

You can't do that when the snippet is scattered inline repeatedly across a large swath of code.

You wouldn't do such scattering anyways, would you? You'd factor these out into a subroutine, and fix any bugs there.

--shmem

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

Comment on Re^2: Module Bloat and the Best Solution

Replies are listed 'Best First'.
Re^3: Module Bloat and the Best Solution by oxone (Friar) on Nov 09, 2007 at 14:44 UTC
Couldn't agree more with your point about bugs in CPAN modules becoming your problem. Excepting core modules, this happens a lot in my experience. I now have a growing personal collection of hacked and patched modules with fixes to significant bugs which have been reported but not yet fixed on CPAN, and that includes such well-respected examples as CGI::Session. CPAN's a great resource, you have to factor in the extra time it takes to evaluate, test, and possibly fix what you find there.	[reply]

Replies are listed 'Best First'.

Re^3: Module Bloat and the Best Solution
by oxone (Friar) on Nov 09, 2007 at 14:44 UTC

Couldn't agree more with your point about bugs in CPAN modules becoming your problem. Excepting core modules, this happens a lot in my experience. I now have a growing personal collection of hacked and patched modules with fixes to significant bugs which have been reported but not yet fixed on CPAN, and that includes such well-respected examples as CGI::Session. CPAN's a great resource, you have to factor in the extra time it takes to evaluate, test, and possibly fix what you find there.

[reply]