Author: larry
Date: Fri Sep 14 11:14:45 2007
New Revision: 14463
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
doc/trunk/design/syn/S11.pod
doc/trunk/design/syn/S12.pod
Log:
typos and nobreak spaces
Modified: doc/trunk/design/syn/S02.pod
==============================================================================
--- doc/trunk/design/syn/S02.pod (original)
+++ doc/trunk/design/syn/S02.pod Fri Sep 14 11:14:45 2007
@@ -102,8 +102,8 @@
=item *
-POD sections may be used reliably as multiline comments in Perl 6.
-Unlike in Perl 5, POD syntax now requires that C<=begin comment>
+POD sections may be used reliably as multiline comments in Perl 6.
+Unlike in Perl 5, POD syntax now requires that C<=begin comment>
and C<=end comment> delimit a POD block correctly without the need
for C<=cut>. (In fact, C<=cut> is now gone.) The format name does
not have to be C<comment> -- any unrecognized format name will do
@@ -216,7 +216,7 @@
Some languages such as C allow you to escape newline characters
to combine lines. Other languages (such as regexes) allow you to
-backslash a space character for various reasons. Perl 6 generalizes
+backslash a space character for various reasons. Perl 6 generalizes
this notion to any kind of whitespace. Any contiguous whitespace
(including comments) may be hidden from the parser by prefixing it
with C<\>. This is known as the "unspace". An unspace can suppress
@@ -254,7 +254,7 @@
$object\ .say();
$object\#{ your ad here }.say
-Anther normal use of a you-don't-see-this-space is typically to put
+Another normal use of a you-don't-see-this-space is typically to put
a dotted postfix on the next line:
$object\ # comment
@@ -1515,7 +1515,7 @@
Also, in the absence of another sigil, C<::> can serve as its own
sigil indicating intentional use of a not-yet-declared package name.
-Unlike in Perl 5, if a sigil is followed by comma, semicolon, colon,
+Unlike in Perl 5, if a sigil is followed by comma, semicolon, colon,
or any kind of bracket or whitespace (including Unicode brackets and
whitespace), it will be taken to be a sigil without a name rather
than a punctuational variable. This allows you to use sigils as coercion
@@ -2762,15 +2762,15 @@
There are two possible ways to parse heredocs. One is to look ahead
for the newline and grab the lines corresponding to the heredoc, and
-then parse the rest of the original line. This is how Perl 5 does it.
-Unfortunately this suffers from the problem pervasive in Perl 5 of
+then parse the rest of the original line. This is how Perl 5 does it.
+Unfortunately this suffers from the problem pervasive in Perl 5 of
multi-pass parsing, which is masked somewhat because there's no way
-to hide a newline in Perl 5. In Perl 6, however, we can use "unspace"
+to hide a newline in Perl 5. In Perl 6, however, we can use "unspace"
to hide a newline, which means that an algorithm looking ahead to find
the newline must do a full parse (with possible untoward side effects)
in order to locate the newline.
-Instead, Perl 6 takes the one-pass approach, and just lazily queues
+Instead, Perl 6 takes the one-pass approach, and just lazily queues
up the heredocs it finds in a line, and waits until it sees a "real"
newline to look for the text and attach it to the appropriate heredoc.
The downside of this approach is a slight restriction--you may not use
Modified: doc/trunk/design/syn/S04.pod
==============================================================================
--- doc/trunk/design/syn/S04.pod (original)
+++ doc/trunk/design/syn/S04.pod Fri Sep 14 11:14:45 2007
@@ -132,7 +132,7 @@
=head1 The Relationship of Blocks and Statements
The return value of a block is the value of its final statement.
-(This is subtly different from Perl 5's behavior, which was to return
+(This is subtly different from Perl 5's behavior, which was to return
the value of the last expression evaluated, even if that expression
was just a conditional.)
@@ -203,7 +203,7 @@
branch, the return value is C<undef> in item context and C<()> in
list context.
-The C<unless> statement does not allow an C<elsif> or C<else> in Perl 6.
+The C<unless> statement does not allow an C<elsif> or C<else> in Perl 6.
The value of the conditional expression may be optionally bound to
a closure parameter:
Modified: doc/trunk/design/syn/S06.pod
==============================================================================
--- doc/trunk/design/syn/S06.pod (original)
+++ doc/trunk/design/syn/S06.pod Fri Sep 14 11:14:45 2007
@@ -1399,7 +1399,7 @@
has a signature, because the autogenerated signature would conflict with that.
Placeholder names consisting of a single uppercase letter are disallowed,
not because we're mean, but because it helps us catch references to
-obsolete Perl 5 variables such as $^O.
+obsolete Perl 5 variables such as $^O.
=head1 Properties and traits
@@ -1758,7 +1758,7 @@
If any function called as part of a return list asks what its context
is, it will be told it was called in list context regardless of the
eventual binding of the returned C<Capture>. (This is quite
-different from Perl 5, where a C<return> statement always propagates its
+different from Perl 5, where a C<return> statement always propagates its
caller's context to its own argument(s).) If that is not the
desired behavior you must coerce the call to an appropriate context,
(or declare the return type of the function to perform such a coercion).
Modified: doc/trunk/design/syn/S09.pod
==============================================================================
--- doc/trunk/design/syn/S09.pod (original)
+++ doc/trunk/design/syn/S09.pod Fri Sep 14 11:14:45 2007
@@ -660,7 +660,7 @@
resulting number of elements exceeds the defined size.
Note that the behaviour of negative indices in Perl 6 is
-different to that in Perl 5:
+different to that in Perl 5:
# Perl 5...
............_____________________________..................
Modified: doc/trunk/design/syn/S11.pod
==============================================================================
--- doc/trunk/design/syn/S11.pod (original)
+++ doc/trunk/design/syn/S11.pod Fri Sep 14 11:14:45 2007
@@ -217,9 +217,9 @@
versions) of Perl they are expecting to run under, so that future
versions of Perl can emulate older versions of Perl (or give a cogent
explanation of why they cannot). This will allow the language to
-evolve without breaking existing widely used modules. (Perl 5 library
+evolve without breaking existing widely used modules. (Perl 5 library
policy is notably lacking here; it would induce massive breakage even
-to change Perl 5 to make strictness the default.) If a CPAN module
+to change Perl 5 to make strictness the default.) If a CPAN module
breaks because it declares that it supports future versions of Perl
when it doesn't, then it must be construed to be the module's fault,
not Perl's. If Perl evolves in a way that does not support emulation
@@ -353,7 +353,7 @@
to guarantee that you get the unembraced Perl. C<:-)>
-To allow a version specification that works with both Perl 5 and 6, we
+To allow a version specification that works with both Perl 5 and Perl 6, we
use variants of the "v6" pseudomodule. This form specifically allows
use of a subsequent hyphenated identifier.
Before the full specification of Perl 6.0.0 is released, you can use C<alpha>
@@ -452,7 +452,7 @@
use v6-alpha;
-Actually, if you're running a parser that is aware of Perl 6, you
+Actually, if you're running a parser that is aware of Perl 6, you
can just start your main program with any of:
use v6;
Modified: doc/trunk/design/syn/S12.pod
==============================================================================
--- doc/trunk/design/syn/S12.pod (original)
+++ doc/trunk/design/syn/S12.pod Fri Sep 14 11:14:45 2007
@@ -242,13 +242,13 @@
$obj.'$methodname'(1,2,3) # no interpolation; call method with $ in name!
[Note: to help catch the mistaken use of C<< infix:<.> >> as a string
-concatenation operator, Perl 6 will warn you about "useless use of
+concatenation operator, Perl 6 will warn you about "useless use of
quotes" at compile time if the string inside quotes is an identifier.
(It does not warn about non-identifier strings, but such strings are
likely to produce missing method errors at run time in any case.)
Also, if there is whitespace around an intended C<.> concatenation,
it cannot be parsed as a method call at all; instead if fails at
-compile time because standard Perl 6 has a pseudo C<< infix:<.> >> operator
+compile time because standard Perl 6 has a pseudo C<< infix:<.> >> operator
that always fails at compile time.]
For situations where you already have a method located, you
@@ -889,7 +889,7 @@
to the C<proto> are also shared by the routines within its scope,
so a C<proto> definition can be used to factor out common traits.
This is particularly useful for establishing grammatical categories
-in a grammar by declaring a C<proto> C<token> or C<proto> C<rule>. (Perl 6's
+in a grammar by declaring a C<proto> C<token> or C<proto> C<rule>. (Perl 6's
grammar does this, for instance.)
You can have multiple C<multi> variables of the same name in the
