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 three dots under the longest token rule. (The long dot : +does not count as a longer token because the longest-token rule only : +applies to the fixed prefix of any rule with variable components.)
Yes, before anyone else points it out to me, that still doesn't quite make sense, insofar as the long-dot rule has to take precedence over postfix ... if there is trailing whitespace. I think the long-dot rule is built into the parser rather than falling out of the longest-token rule. And the long-dot rule has to look ahead to see if there is whitespace following. Seems a lot more benign than the previous forms of lookahead though. Definitely easier to parse visually, I think. Larry
