Re^2: w/Modules and w/o Modules

Replies are listed 'Best First'.
Re^3: w/Modules and w/o Modules by chromatic (Archbishop) on Sep 20, 2011 at 19:57 UTC
when should I not use a module? When your own code is better than the module, and when it's not worth your time to create and maintain your own code instead of using the module. Improve your skills with Modern Perl: the free book.	[reply]
Re^4: w/Modules and w/o Modules by raybies (Chaplain) on Sep 20, 2011 at 22:09 UTC
...or when there isn't a module that does what you want... ...or it doesn't install and it takes you longer to try to figure out how the module works or isn't working rather than writing it yourself... ...or when you're confined to an old version of Perl that doesn't support the module you might've used... In my case, since I cannot directly attach to CPAN from my dev machine, if modules have a lot of dependencies, I find the install hassle to be a pain... as I have to dl it on one machine, burn it to a disk, then install it by hand on my dev machine... Of course when there is a module that does what I want, and it works and I don't have to implement it myself, I cry tears of joy... :)	[reply]
Re^5: w/Modules and w/o Modules by chromatic (Archbishop) on Sep 20, 2011 at 23:07 UTC
...or when you're confined to an old version of Perl that doesn't support the module you might've used... In my case, since I cannot directly attach to CPAN from my dev machine... My sympathies. It must be difficult to work in an environment that doesn't trust its skilled professionals. I find the install hassle to be a pain... as I have to dl it on one machine, burn it to a disk, then install it by hand on my dev machine... Have you seen CPAN::Mini? You could save yourself a lot of time. Improve your skills with Modern Perl: the free book.	[reply]
Re^6: w/Modules and w/o Modules by raybies (Chaplain) on Sep 21, 2011 at 12:44 UTC