Larry Wall schreef:
> before anyone else points it out to me
> I think the long-dot
> rule is built into the parser rather than falling out of the
> longest-token rule.
I think so too, but why then cling to the dot?
s:p5/[\][#][^\]*[#][\]// (does not match \#\ )
The backslash is no
On Fri, Apr 07, 2006 at 10:07:55PM +0100, Nicholas Clark wrote:
: On Fri, Apr 07, 2006 at 01:11:15PM -0700, Larry Wall wrote:
: > On Fri, Apr 07, 2006 at 01:04:38PM -0700, [EMAIL PROTECTED] wrote:
: > : +The long dot form of the C<...> postfix is C<0. ...> rather than
: > : +C<0. > because the
On Fri, Apr 07, 2006 at 01:11:15PM -0700, Larry Wall wrote:
> On Fri, Apr 07, 2006 at 01:04:38PM -0700, [EMAIL PROTECTED] wrote:
> : +The long dot form of the C<...> postfix is C<0. ...> rather than
> : +C<0. > because the long dot eats the first dot after the whitespace.
> : +It does not foll
On Fri, Apr 07, 2006 at 01:04:38PM -0700, [EMAIL PROTECTED] wrote:
: +The long dot form of the C<...> postfix is C<0. ...> rather than
: +C<0. > because the long dot eats the first dot after the whitespace.
: +It does not follow that you can write C<0> because that would
: +take the first t
Author: larry
Date: Fri Apr 7 13:04:37 2006
New Revision: 8609
Modified:
doc/trunk/design/syn/S02.pod
Log:
More long dot cleanup.
Modified: doc/trunk/design/syn/S02.pod
==
--- doc/trunk/design/syn/S02.pod(or
