summaryrefslogtreecommitdiff
path: root/pod/perlcall.pod
diff options
context:
space:
mode:
authorDaniel Chetlin <daniel@chetlin.com>2000-08-03 17:22:44 -0700
committerJarkko Hietaniemi <jhi@iki.fi>2000-08-04 12:26:33 +0000
commit90fdbbb75512007b809510f03fc507ff5c145e16 (patch)
tree49ec382ac772ca6ab35d1efbd12fadd4a242db02 /pod/perlcall.pod
parent9300ef0fea165be49d88144848cf782932f9cfb9 (diff)
downloadperl-90fdbbb75512007b809510f03fc507ff5c145e16.tar.gz
Re: Array vs. List context
Message-ID: <20000804002244.A5924@ilmd.chetlin.org> p4raw-id: //depot/perl@6522
Diffstat (limited to 'pod/perlcall.pod')
-rw-r--r--pod/perlcall.pod8
1 files changed, 4 insertions, 4 deletions
diff --git a/pod/perlcall.pod b/pod/perlcall.pod
index 148b24b51b..94edd342f4 100644
--- a/pod/perlcall.pod
+++ b/pod/perlcall.pod
@@ -201,8 +201,8 @@ As with G_SCALAR, this flag has 2 effects:
=item 1.
-It indicates to the subroutine being called that it is executing in an
-array context (if it executes I<wantarray> the result will be true).
+It indicates to the subroutine being called that it is executing in a
+list context (if it executes I<wantarray> the result will be true).
=item 2.
@@ -355,7 +355,7 @@ use of this flag.
As mentioned above, you can determine the context of the currently
executing subroutine in Perl with I<wantarray>. The equivalent test
can be made in C by using the C<GIMME_V> macro, which returns
-C<G_ARRAY> if you have been called in an array context, C<G_SCALAR> if
+C<G_ARRAY> if you have been called in a list context, C<G_SCALAR> if
in a scalar context, or C<G_VOID> if in a void context (i.e. the
return value will not be used). An older version of this macro is
called C<GIMME>; in a void context it returns C<G_SCALAR> instead of
@@ -806,7 +806,7 @@ Notes
=item 1.
-We wanted array context, so G_ARRAY was used.
+We wanted list context, so G_ARRAY was used.
=item 2.