Author: larry Date: Mon Sep 1 18:12:53 2008 New Revision: 14579 Modified: doc/trunk/design/syn/S04.pod
Log: clarify that statement introducers may not use function syntax, which is reserved for user functions of the same name Modified: doc/trunk/design/syn/S04.pod ============================================================================== --- doc/trunk/design/syn/S04.pod (original) +++ doc/trunk/design/syn/S04.pod Mon Sep 1 18:12:53 2008 @@ -12,9 +12,9 @@ Maintainer: Larry Wall <[EMAIL PROTECTED]> Date: 19 Aug 2004 - Last Modified: 16 July 2008 + Last Modified: 1 Sep 2008 Number: 4 - Version: 68 + Version: 69 This document summarizes Apocalypse 4, which covers the block and statement syntax of Perl. @@ -645,9 +645,10 @@ establish a dynamic scope without necessarily establishing a lexical scope. (You can always establish a lexical scope explicitly by using the block form of argument.) As statement introducers, all these -keywords must be followed by whitespace. You can say something -like C<try({...})>, but then you are calling it using function call -syntax instead, in which case the C<Code> argument must be a block. +keywords must be followed by whitespace. (You can say something +like C<try({...})>, but then you are calling the C<try()> function +using function call syntax instead, and since Perl does not supply +such a function, it will be assumed to be a user-defined function.) For purposes of flow control, none of these forms are considered loops, but they may easily be applied to a normal loop.