in reply to Why use strict/warnings?

Just thought I'd throw in something else that I haven't seen posted yet: saying

use strict;

lets anyone else who reads your code know that you know what you're doing, which makes a difference when they read it. (They can, for instance, assume that if they see an unqualified variable in a subroutine, it's local to that sub, and not some sort of magic state that affects other parts of the code.) This makes your code easier to read, which makes everyone happier.

Replies are listed 'Best First'.
Re: Re: Why use strict/warnings?
by mugwumpjism (Hermit) on Aug 10, 2001 at 01:39 UTC

    That's all well and good, until you see the next line:

    use vars qw($CONFIG $my_loop_var $fileno $window_size ....)

    Perhaps we need a new pragma:

    use Schwern;   # Schwern is my bitch.

    I'm sure the people reading the code would get the gist then.