diff options
| author | Matt Kraai <kraai@ftbfs.org> | 2008-04-13 08:56:37 -0700 |
|---|---|---|
| committer | Rafael Garcia-Suarez <rgarciasuarez@gmail.com> | 2008-04-18 12:51:41 +0000 |
| commit | 432fb0a0d3d35f4a3937889f2c65086f2da4cd89 (patch) | |
| tree | 62a3a5c8a96e78247a35a7142d6934195664169c /pod/perlintro.pod | |
| parent | 514f8bac36131e6028eb1b3cae7cb2afa3328a60 (diff) | |
| download | perl-432fb0a0d3d35f4a3937889f2c65086f2da4cd89.tar.gz | |
[perl #52860] [PATCH] Incorrect variable name in perlintro
From: Matt Kraai (via RT) <perlbug-followup@perl.org>
Message-ID: <rt-3.6.HEAD-25460-1208127396-514.52860-75-0@perl.org>
p4raw-id: //depot/perl@33713
Diffstat (limited to 'pod/perlintro.pod')
| -rw-r--r-- | pod/perlintro.pod | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlintro.pod b/pod/perlintro.pod index b069c51960..9973fd62c1 100644 --- a/pod/perlintro.pod +++ b/pod/perlintro.pod @@ -302,7 +302,7 @@ are defined. Using C<my> in combination with a C<use strict;> at the top of your Perl scripts means that the interpreter will pick up certain common programming errors. For instance, in the example above, the final -C<print $b> would cause a compile-time error and prevent you from +C<print $y> would cause a compile-time error and prevent you from running the program. Using C<strict> is highly recommended. =head2 Conditional and looping constructs |