Author: larry Date: Sat Apr 15 18:38:36 2006 New Revision: 8700 Modified: doc/trunk/design/syn/S02.pod doc/trunk/design/syn/S06.pod
Log: Cleanup typos. Modified: doc/trunk/design/syn/S02.pod ============================================================================== --- doc/trunk/design/syn/S02.pod (original) +++ doc/trunk/design/syn/S02.pod Sat Apr 15 18:38:36 2006 @@ -12,9 +12,9 @@ Maintainer: Larry Wall <[EMAIL PROTECTED]> Date: 10 Aug 2004 - Last Modified: 10 Apr 2006 + Last Modified: 15 Apr 2006 Number: 2 - Version: 22 + Version: 23 This document summarizes Apocalypse 2, which covers small-scale lexical items and typological issues. (These Synopses also contain @@ -533,9 +533,9 @@ positional, named, and so on. Like C<List> objects, C<Capture> objects are immutable in the abstract, but -evaluates its arguments lazily. Before everything inside a C<Capture> are +evaluate their arguments lazily. Before everything inside a C<Capture> is fully evaluated (which happens at compile time when all the arguments are -constants), the eventual value may well be unknown. All we know is that is +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. C<Capture> objects may contain multiple unresolved iterators such as pipes Modified: doc/trunk/design/syn/S06.pod ============================================================================== --- doc/trunk/design/syn/S06.pod (original) +++ doc/trunk/design/syn/S06.pod Sat Apr 15 18:38:36 2006 @@ -13,9 +13,9 @@ Maintainer: Larry Wall <[EMAIL PROTECTED]> Date: 21 Mar 2003 - Last Modified: 6 Apr 2006 + Last Modified: 15 Apr 2006 Number: 6 - Version: 23 + Version: 24 This document summarizes Apocalypse 6, which covers subroutines and the @@ -579,7 +579,7 @@ so that you can use more descriptive internal parameter names without imposing inconveniently long external labels on named arguments. -Capture that correspond to named parameters are evaluated in scalar +Arguments that correspond to named parameters are evaluated in scalar context. They can only be passed by name, so it doesn't matter what order you pass them in, so long as they don't intermingle with any positional arguments:
