comment on

'use strict' would find this error immediately and tell you exactly were it was.

Okay I'll bite, what is wrong with the following?

my @cleanup = ('an', 'array', 'of', 'words');

for (my $i = 0; $i < scalar(@c1eanup); $i++) {
   $cleanup[$i] =~ s/oldserv001/newserv001/ig;
}
[download]

I couldn't spot it and even plugging it into a script with -w and use strict gave no clues either. So if it works with strictures why is it wrong?

Warnings and strictures are great during development, they are much like lint for C programs. However, it shouldn't be necessary for production code, and that is one thing that people forget. I would be wary of any code that didn't have use strict at the top, even if it was commented out, as the chances are it hasn't been run with strictures and as such, possibly not full tested.

Warnings and strictures are there to help you spot glaring and subtle errors, which otherwise might show themselves in many weird and wonderful ways, and take a lot longer to figure out otherwise.

--
Barbie | Birmingham Perl Mongers | http://birmingham.pm.org/

In reply to Re: Re: Use Strict by barbie
in thread Add use strict to this? by ironpaw

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Just another Perl shrine
	PerlMonks