Modified:
doc/trunk/design/syn/S02.pod
Log:
* upper/lowercase English nit fix for the last patch as suggested by TimToady
Modified: doc/trunk/design/syn/S02.pod
==============================================================================
--- doc/trunk/design/syn/S02.pod (original)
+++ doc/trunk/design/syn/S02.pod Sat Apr 1 20:10:15 2006
@@ -401,8 +401,8 @@
%$args; # same as '$args as Hash" or "Hash($args)"
&$args; # same as '$args as Code" or "Code($args)"
-When cast into an array, you can access all the positional arguments; Into a
-hash, all named arguments; Into a scalar, the invocant; Into code, its slurpy
+When cast into an array, you can access all the positional arguments; into a
+hash, all named arguments; into a scalar, the invocant; into code, its slurpy
nameless block.
All prefix sigil operators accept one positional argument, evaluated in
a> Author: autrijus
a> Date: Sat Apr 1 20:10:15 2006
a> New Revision: 8532
a> Modified:
a> doc/trunk/design/syn/S02.pod
a> Log:
a> * upper/lowercase English nit fix for the last patch as suggested
a> by TimToady
you might as well attribute the s:g/Into/into/ to dr. ruud. all timtoady
did was correct dr. ruud's p5 s///g into p6's s:g///. if we are going to
pick nits this small, then the tiny amount of credit is worth bestowing
upon the correct contributor. :)
one of these days when i have tuits of large circumference, i will do a
nit pass over as much of the A/E/S as i can handle before my brain
explodes. having done tech editing for perl books is good training for
this. in fact it would be a good idea to have several such passes by
those with editing skill before those docs are 'released'. some of the
concepts are so new to so many and are bleeding edge that the wording
used has to be extra clean of nits and such stuff as dangling pronouns
and other common flaws of technical writing.
speaking of bleeding edge? what do you call the opposite of that?
<spoiler space>
the coagulated edge.
uri
--
Uri Guttman ------ u...@stemsystems.com -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
AT> Uri Guttman wrote:
>> one of these days when i have tuits of large circumference, i will do a
>> nit pass over as much of the A/E/S as i can handle before my brain
>> explodes. having done tech editing for perl books is good training for
>> this. in fact it would be a good idea to have several such passes by
>> those with editing skill before those docs are 'released'. some of the
>> concepts are so new to so many and are bleeding edge that the wording
>> used has to be extra clean of nits and such stuff as dangling pronouns
>> and other common flaws of technical writing.
AT> Indeed. If we can arrange to have a "docathon" of factoring S* via such
AT> reviewing passes into Perl6::Doc::{Spec,Overview,Tutorial} documents,
AT> that can greatly speed up Perl 6 adoption.
AT> Got some cycles at YAPC::NA::Chicago? :)
i dunno now. is there going to be a hackathon like last year before
toronto? i could possibly get there early for some of that and get some
of that manic group energy focused on the docs. hell, i would do it just
to try to grok some of the stuff that is flying around. :)
so is anyone going to volunteer their place for this?
Indeed. If we can arrange to have a "docathon" of factoring S* via such
reviewing passes into Perl6::Doc::{Spec,Overview,Tutorial} documents,
that can greatly speed up Perl 6 adoption.
Got some cycles at YAPC::NA::Chicago? :)
Audrey