I try to use module when coding in Perl only if there is no other way. I just like to know what is happening in my script in every line. If you "overuse" other people's work you can run into trouble one day :)
(This is my general opinion about mass using modules/classes when developing new application, we can discuss it here if you want.) | [reply] |
| [reply] |
Come on, this is not the case. I only explained why even after I knew such a module exists I tried to work around. In such a situation built-in module is ok.
| [reply] |
| [reply] |
Yes, as I have full control. I can make some mistakes but then I can debug and fix them.
Of course I mean scripts, applications made for myself. Professional coding in a huge company will depend on third party libraries/classes/modules although GOOD companies with strong background make their own libraries.
- 1 example: see gaming industry; they don't buy graphic engines they create them from scratch
- 2 example: we use reporting framework in our company and we were in trouble last year as the magnificent engine doesn't support 64 bit environment (and yes we paid for it lot of money)
To sum up:
-
my own software is better if I am the author (I can write a module too),
-
even in professional world of developing it is better to create own libraries if the company can afford it
| [reply] |
