Hello,
Okay. I am trying to understand scoping on perl and after several tries, a FAQ and several perldoc readings, it seems perl prefers reusable code (ie modules or libraries) in .pm files. That way you can 'use' such files in your program. Now, I had coded all my 'modules' in .pl files, and having several require statements to incorporate all that code into my main program. Problem is I wanted to 'use strict' but of course I am having huge scoping issues. What I want to know, is if it is indeed better to build .pm files to just requireING external files. Is is actually faster to do .pm modules, or does it just make it easier for the compiler to 'catch' errors? Or is it just 'good style'? Also, if it really comes to that I need to build .pm files, should those go in the perl directory on the server? I would like them on another location, and what I do is part of a big application, so I might not be able to add stuff to @INC (unless of course I can on my subprogram routines). Please help, since I cannot seem to find a definitive answer about this.
Regards,
Javier Moreno
==============
Softtek/GXS
EFS NearShore - TradeWeb 2nd Tier
...when you have eliminated the impossible, whatever remains, however improbable, must be the truth.
- Sherlock Holmes
