in reply to Re: Use Strict
in thread Add use strict to this?

'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/

Replies are listed 'Best First'.
Worked for me.
by cfreak (Chaplain) on Jul 17, 2003 at 13:46 UTC

    Notice the scalar statement. The array 'cleanup' was spelled with a 1 instead of a lowercase L. At first I thought you were right but then I realized I copied the code and didn't put use strict at the top. After doing so, strict caught the error :). What Perl are you using that it didn't?

    Lobster Aliens Are attacking the world!
[reply]
[d/l]
[select]
      Try a copy and paste from the example you posted. There is no '1' it's a lowercase 'L'.

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

[reply]
[reply]

In Section Seekers of Perl Wisdom