summaryrefslogtreecommitdiff
path: root/pod/perlfaq6.pod
diff options
context:
space:
mode:
authorGurusamy Sarathy <gsar@cpan.org>1998-07-22 05:10:53 +0000
committerGurusamy Sarathy <gsar@cpan.org>1998-07-22 05:10:53 +0000
commit92c2ed055315fc5be2c58f97c40236945f31f32e (patch)
treeccace68daba971343b831dfc0ce5fd0e0647e385 /pod/perlfaq6.pod
parent407eff0f25e20d3ed6ccfe2097b366fd28d8e3c4 (diff)
downloadperl-92c2ed055315fc5be2c58f97c40236945f31f32e.tar.gz
perlfaq update from From Tom Christiansen and Nathan Torkington
(removes all mention of training courses from perlfaq*.pod) p4raw-id: //depot/perl@1621
Diffstat (limited to 'pod/perlfaq6.pod')
-rw-r--r--pod/perlfaq6.pod12
1 files changed, 5 insertions, 7 deletions
diff --git a/pod/perlfaq6.pod b/pod/perlfaq6.pod
index 053e28496d..488a27c83a 100644
--- a/pod/perlfaq6.pod
+++ b/pod/perlfaq6.pod
@@ -1,6 +1,6 @@
=head1 NAME
-perlfaq6 - Regexps ($Revision: 1.21 $, $Date: 1998/06/22 04:23:04 $)
+perlfaq6 - Regexps ($Revision: 1.22 $, $Date: 1998/07/16 14:01:07 $)
=head1 DESCRIPTION
@@ -545,12 +545,10 @@ L<perlfaq2>).
=head2 What's wrong with using grep or map in a void context?
-Strictly speaking, nothing. Stylistically speaking, it's not a good
-way to write maintainable code. That's because you're using these
-constructs not for their return values but rather for their
-side-effects, and side-effects can be mystifying. There's no void
-grep() that's not better written as a C<for> (well, C<foreach>,
-technically) loop.
+Both grep and map build a return list, regardless of their context.
+This means you're making Perl go to the trouble of building up a
+return list that you then just ignore. That's no way to treat a
+programming language, you insensitive scoundrel!
=head2 How can I match strings with multibyte characters?