Change 13702 by jhi@alpha on 2001/12/15 17:18:49
Subject: [PATCH] perlstyle.pod nit on warnings
From: Autrijus Tang <[EMAIL PROTECTED]>
Date: Sat, 15 Dec 2001 04:24:34 -0800
Message-ID: <[EMAIL PROTECTED]>
Affected files ...
.... //depot/perl/pod/perlstyle.pod#10 edit
Differences ...
==== //depot/perl/pod/perlstyle.pod#10 (text) ====
Index: perl/pod/perlstyle.pod
--- perl/pod/perlstyle.pod.~1~ Sat Dec 15 10:30:06 2001
+++ perl/pod/perlstyle.pod Sat Dec 15 10:30:06 2001
@@ -10,11 +10,10 @@
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<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.
+portions of code via the C<no 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.
Regarding aesthetics of code lay out, about the only thing Larry
cares strongly about is that the closing curly bracket of
@@ -261,10 +260,9 @@
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 C<use warnings> (or B<-w>) in effect
-Consider giving away
-your code. Consider changing your whole world view. Consider... oh,
-never mind.
+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.
=item *
End of Patch.
