Brent Clark <mailto:[EMAIL PROTECTED]> wrote:
: Hi list
:
: I have a problem whereby another new programmer (like myself)
: likes NOT to use strict in his code where by I do.
:
: The problem is that I have is that he as writting a pm file and
: basically just did is as so:
[snipped code]
One short-term solution might be to declare all the variables
from the module using "our" at the top of your code. Any time the
module is updated, you'll need to check the variables again.
Another short-term solution is to turn off strict in the script
with a detailed reason. Make a big deal about it.
# Turning off strictures to accommodate foreign module.
no strict 'var';
use PM::File;
This alerts anyone (who reads the code) there is a problem with
the module. You should be able to test most of your of subroutines
without the results of this suspect module and under strict
conditions.
All the long-term solutions require the new programmer to be a
better programmer. Only you can decide what solution is best there.
I assume you already know that. I imagine that having your superiors
understand the importance of strictures and warnings would be a
helpful first step.
HTH,
Charles K. Clarkson
--
Mobile Homes Specialist
254 968-8328
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>
