Author: larry
Date: Wed Apr 2 11:02:36 2008
New Revision: 14537
Modified:
doc/trunk/design/syn/S02.pod
doc/trunk/design/syn/S03.pod
Log:
typo from Jon Lang++
clarify innards of () and [] slightly
Modified: doc/trunk/design/syn/S02.pod
==============================================================================
--- doc/trunk/design/syn/S02.pod (original)
+++ doc/trunk/design/syn/S02.pod Wed Apr 2 11:02:36 2008
@@ -1489,7 +1489,7 @@
&foo($arg1, $arg2);
-Whitespace is not allowed before the parens because it it is parsed as
+Whitespace is not allowed before the parens because it is parsed as
a postfix. As with any postfix, there is also a corresponding C<.()>
operator, and you may use the "unspace" form to insert optional
whitespace and comments between the backslash and either of the
Modified: doc/trunk/design/syn/S03.pod
==============================================================================
--- doc/trunk/design/syn/S03.pod (original)
+++ doc/trunk/design/syn/S03.pod Wed Apr 2 11:02:36 2008
@@ -85,7 +85,7 @@
This isn't really a precedence level, but it's in here because no operator
can have tighter precedence than a term. See S02 for longer descriptions of
-various terms.
+various terms. Here are some examples.
=over
@@ -137,7 +137,10 @@
[1,2,3]
-Provides list context inside.
+Provides list context inside. (Technically, it really provides a
+"semilist" context, which is a semicolon-separated list of statements,
+each of which is interpreted in list context and then concatenated
+into the final list.)
=item *
@@ -213,11 +216,14 @@
=item *
-Circumfixed subexpressions
+Subexpressions circumfixed by parentheses
(1+2)
-Circumfixed items are treated like a term on the outside.
+Parentheses are parsed on the inside as a semicolon-separated list
+of statements, which (unlike the statements in a block) returns the results
+of all the statements concatenated together as a C<List> of C<Capture>.
+How that is subsequently treated depends on its eventual binding.
=item *
