diff options
| author | Piotr Fusik <pfusik@op.pl> | 2005-07-31 14:50:04 +0200 |
|---|---|---|
| committer | H.Merijn Brand <h.m.brand@xs4all.nl> | 2005-08-02 10:39:51 +0000 |
| commit | 3c4b39bee8832007b7e91bfce8701d34cacab411 (patch) | |
| tree | 190f72b72255db85e5c78f68a0d0047692aab3a9 /lib/Switch.pm | |
| parent | db30010093a0bacd16d1fa3fd1bd5397da6479d3 (diff) | |
| download | perl-3c4b39bee8832007b7e91bfce8701d34cacab411.tar.gz | |
Typos in *.p[lm]
From: "Piotr Fusik" <pfusik@op.pl>
Message-ID: <001401c595bd$dccb5d80$0bd34dd5@piec>
p4raw-id: //depot/perl@25261
Diffstat (limited to 'lib/Switch.pm')
| -rw-r--r-- | lib/Switch.pm | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/Switch.pm b/lib/Switch.pm index 646e7cef65..4b1b3e27f3 100644 --- a/lib/Switch.pm +++ b/lib/Switch.pm @@ -681,7 +681,7 @@ Fall-though (trying another case after one has already succeeded) is usually a Bad Idea in a switch statement. However, this is Perl, not a police state, so there I<is> a way to do it, if you must. -If a C<case> block executes an untargetted C<next>, control is +If a C<case> block executes an untargeted C<next>, control is immediately transferred to the statement I<after> the C<case> statement (i.e. usually another case), rather than out of the surrounding C<switch> block. @@ -713,7 +713,7 @@ For example: case /\d/ { handle_dig_any(); } } -If an untargetted C<last> statement is executed in a case block, this +If an untargeted C<last> statement is executed in a case block, this immediately transfers control out of the enclosing C<switch> block (in other words, there is an implicit C<last> at the end of each normal C<case> block). Thus the previous example could also have been |