Author: larry Date: Fri Jun 15 12:20:51 2007 New Revision: 14423 Modified: doc/trunk/design/syn/S03.pod doc/trunk/design/syn/S12.pod
Log: minor clarifications to previous Modified: doc/trunk/design/syn/S03.pod ============================================================================== --- doc/trunk/design/syn/S03.pod (original) +++ doc/trunk/design/syn/S03.pod Fri Jun 15 12:20:51 2007 @@ -222,7 +222,11 @@ Note that this may occur only where a term is expected. Where a postfix is expected, it is a postfix. If only an infix is expected -(that is, after a term with intervening whitespace), it is a syntax error. +(that is, after a term with intervening whitespace), C<.meth> is a +syntax error. (The C<.=meth> form is allowed there only because there +is a special C<.=> infix assignment operator that is equivalent in +semantics to the method call form but that allows whitespace between +the C<=> and the method name.) =item * Modified: doc/trunk/design/syn/S12.pod ============================================================================== --- doc/trunk/design/syn/S12.pod (original) +++ doc/trunk/design/syn/S12.pod Fri Jun 15 12:20:51 2007 @@ -232,8 +232,8 @@ 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 no C<< infix:<.> >> operator -unless the user happens to have defined one (bad idea).] +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 can use a simple scalar variable in place of method name:
