I have a problem whereby another new programmer (like myself) likes
NOT to
use strict in his code where by I do.
My own anecdote: I didn't think that using the 'strict' or 'warnings'
pragmas was important either, once. And I'm a very novice programmer.
However, when I thought about, I always liked being able to debug my
(shell) scripts as I wrote them; it saves time by testing during, not
after coding. Using those pragmas has helped me a lot since I started
with Perl. More importantly it has forced me to become a better
programmer, to pay attention to scoping.
Good points :) I like to leave it in even after its "done". The reason
is simple:
- you're probably not really done you just think you are until your
boss wants you to add a bunch more stuff to it.
- What if its strict and warnings safe when you test it but the
environment it will be run in is different and creates a not strict or
warnings safe environment? Instead of installing a "tested safe" but not
"running safe" and wonder why it worked before but is giving you blank
stares you'll have info right there to help fix it.
- its not portable and more likely to cause issues that are hard to
track down in a project
- I'd be so ticked to find a module I wanted to use wasn't
strict/warnings safe, module should always be strict/warnings safe
unless there is a really good reason not to, and when your friend thinks
he has good reason its because he is clueless. Please tell me this isn;t
going to be a publicly available module. If it is tell me what it is so
I'll be sure not to use it and also put in your docs all sorts of info
and disclaimers about how "it may be strict warnings safe but then again
it may not since my clueless friend insists on bad practice" :)
As far as the style of the module it looks like really really really old
code, see perldoc perlmod to see how to make a module that works well
and is most portable.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>
