diff options
| author | Gurusamy Sarathy <gsar@cpan.org> | 2000-03-13 21:29:15 +0000 |
|---|---|---|
| committer | Gurusamy Sarathy <gsar@cpan.org> | 2000-03-13 21:29:15 +0000 |
| commit | 9f1b1f2d9ab55954ee07a14c4ab04bd3dd1f99d5 (patch) | |
| tree | f3e99c675e49f21e2edc6600cd4c0b10b14c41d5 /pod/perlstyle.pod | |
| parent | 828c4421567f1da54062ec5edfcc3250be409b16 (diff) | |
| download | perl-9f1b1f2d9ab55954ee07a14c4ab04bd3dd1f99d5.tar.gz | |
lexical warnings update for docs and tests (from Paul Marquess)
p4raw-id: //depot/perl@5712
Diffstat (limited to 'pod/perlstyle.pod')
| -rw-r--r-- | pod/perlstyle.pod | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/pod/perlstyle.pod b/pod/perlstyle.pod index 04aab9854a..bfe5b76713 100644 --- a/pod/perlstyle.pod +++ b/pod/perlstyle.pod @@ -10,7 +10,8 @@ make your programs easier to read, understand, and maintain. The most important thing is to run your programs under the B<-w> flag at all times. You may turn it off explicitly for particular -portions of code via the C<$^W> variable if you must. You should +portions of code via the C<use warnings> pragma or the C<$^W> variable +if you must. You should also always run under C<use strict> or know the reason why not. The C<use sigtrap> and even C<use diagnostics> pragmas may also prove useful. @@ -260,7 +261,8 @@ Line up your transliterations when it makes sense: Think about reusability. Why waste brainpower on a one-shot when you might want to do something like it again? Consider generalizing your code. Consider writing a module or object class. Consider making your -code run cleanly with C<use strict> and B<-w> in effect. Consider giving away +code run cleanly with C<use strict> and C<use warnings> (or B<-w>) in effect +Consider giving away your code. Consider changing your whole world view. Consider... oh, never mind. |