Author: audreyt
Date: Wed Jul 26 07:17:16 2006
New Revision: 10477
Modified:
doc/trunk/design/syn/S02.pod
doc/trunk/design/syn/S04.pod
doc/trunk/design/syn/S06.pod
doc/trunk/design/syn/S09.pod
Log:
* S02, S04, S06, S09: Chase the terminology change of
pipe operator = feed operator and rename all menitons
of pipes in the text. Sometimes a pipe is just a feed...
Modified: doc/trunk/design/syn/S02.pod
==
--- doc/trunk/design/syn/S02.pod(original)
+++ doc/trunk/design/syn/S02.podWed Jul 26 07:17:16 2006
@@ -12,9 +12,9 @@
Maintainer: Larry Wall [EMAIL PROTECTED]
Date: 10 Aug 2004
- Last Modified: 19 July 2006
+ Last Modified: 26 July 2006
Number: 2
- Version: 55
+ Version: 56
This document summarizes Apocalypse 2, which covers small-scale
lexical items and typological issues. (These Synopses also contain
@@ -571,7 +571,7 @@
A variant of C* is the C** term. It is generally understood to
be a multidimension form of C* when that makes sense.
-The C*** variant serves as the insertion point of a list of pipes.
+The C*** variant serves as the insertion point of a list of feeds.
That insertion point may be targeted by piping to C*. See S06.
Other uses for C* will doubtless suggest themselves over time. These
@@ -734,7 +734,7 @@
constants), the eventual value may well be unknown. All we know is
that we have the promise to make the bits of it immutable as they become known.
-CCapture objects may contain multiple unresolved iterators such as pipes
+CCapture objects may contain multiple unresolved iterators such as feeds
or slices. How these are resolved depends on what they are eventually
bound to. Some bindings are sensitive to multiple dimensions while
others are not.
Modified: doc/trunk/design/syn/S04.pod
==
--- doc/trunk/design/syn/S04.pod(original)
+++ doc/trunk/design/syn/S04.podWed Jul 26 07:17:16 2006
@@ -12,9 +12,9 @@
Maintainer: Larry Wall [EMAIL PROTECTED]
Date: 19 Aug 2004
- Last Modified: 21 July 2006
+ Last Modified: 26 July 2006
Number: 4
- Version: 29
+ Version: 30
This document summarizes Apocalypse 4, which covers the block and
statement syntax of Perl.
@@ -503,7 +503,7 @@
The innermost block matching the selection criteria will be exited.
The return value, if any, must be passed as a list. To return pairs
-as part of the value, you can use a pipe:
+as part of the value, you can use a feed operator:
leave == :foo:bar:baz(1) if $leaving;
Modified: doc/trunk/design/syn/S06.pod
==
--- doc/trunk/design/syn/S06.pod(original)
+++ doc/trunk/design/syn/S06.podWed Jul 26 07:17:16 2006
@@ -13,9 +13,9 @@
Maintainer: Larry Wall [EMAIL PROTECTED]
Date: 21 Mar 2003
- Last Modified: 16 July 2006
+ Last Modified: 26 July 2006
Number: 6
- Version: 40
+ Version: 41
This document summarizes Apocalypse 6, which covers subroutines and the
@@ -804,10 +804,10 @@
bar;# $args === \(1,2,3)
bar(); # $args === \()
-=head2 Pipe operators
+=head2 Feed operators
The variadic list of a subroutine call can be passed in separately
-from the normal argument list, by using either of the pipe operators:
+from the normal argument list, by using either of the Ifeed operators:
C == or C == .
Each operator expects to find a call to a variadic receiver on its
@@ -819,19 +819,20 @@
It binds the (potentially lazy) list from the blunt end to the slurpy
parameter(s) of the receiver on the sharp end. In the case of a receiver
-that is a variadic function, the pipe is received as part of its slurpy list.
+that is a variadic function, the feed is received as part of its slurpy list.
So both of the calls above are equivalent to:
grep { $_ % 2 }, @data;
-Note that all such pipes (and indeed all lazy argument lists) supply
+Note that all such feed (and indeed all lazy argument lists) supply
an implicit promise that the code producing the lists may execute
-in parallel with the code receiving the lists. (Pipes, hyperops,
+in parallel with the code receiving the lists. (Feeds, hyperops,
and junctions all have this promise of parallelizability in common,
but differ in interface. Code which violates these promises is
erroneous, and will produce undefined results when parallelized.)
-In particular, a pipeline may not begin and end with the same array.
-(You may, however, assign to an array that is used within a pipeline
+
+In particular, a chain of feeds may not begin and end with the same array.
+(You may, however, assign to an array that is used within a chain
on the right side of the assignment, since list assignment will clear
and copy as necessary to make it work.) That is, this doesn't work:
@@ -841,7 +842,7
