in reply to rename files using regex.

Why would it have to use strict? Larry's well known rename program predates Perl5, so I wouldn't expect it to use strict. Besides, the code is Larry's, and AFAIK, Larry hardly ever uses strict. And neither does Damian for that matter. (Conspiricy?)

There's little value in adding 'use strict' to old programs. Strictness is mostly a development aid.

Abigail

Replies are listed 'Best First'.
strict is useful in all active situations (was Re2: rename files using regex.)
by dragonchild (Archbishop) on Jul 23, 2003 at 15:33 UTC
    Strictness is mostly a development aid.

    I'm going to disagree with that statement. Strictness is both a development aid and a debugging aid. For example, I am attempting to maintain some crappy code that is in production that was originally written by C programmers who don't understand references. By adding strict, I can detect and fail on attempts to use non-references as references. While testing should catch these, it won't catch them all.

    Personally, I feel that if you're maintaining and updating an old program, it should be made strict. (Preferably, I'd add warnings to it, as well, but that's truly a personal preference. I'm anal. *grins*)

    ------
    We are the carpenters and bricklayers of the Information Age.

    Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.

    Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.

Re: Re: rename files using regex.
by djbiv (Scribe) on Jul 23, 2003 at 15:28 UTC
    good notes! I enjoyed your comment, and didn't even think about the snippet pre-dating strict;