Front page | perl.perl5.porters |
Postings from April 2007
April 12, 2007 14:09
Message ID: firstname.lastname@example.org
On 4/12/07, Glenn Linderman <email@example.com> wrote:
> Great stuff! A couple minor nits...
> On approximately 4/12/2007 6:23 AM, came the following characters from
> the keyboard of Abigail:
> > =item \C
> > C<\C> always matches a single octet, even if the source string is encoded
> > in UTF-8 format, and the character to be matched is a multi-octed character.
> > C<\C> is new in perl5.10.
> > Mnemonic: oI<C>tet.
> multi-octet ? rather than multi-octed ?
> > =item \v, \V
> > Both C<\v> and C<\V> are new in perl5.10, and are shortcuts for
> > C<(*PRUNE)> and C<(*SKIP)>. See L<???>.
> > If the regular expression engines backtracks over C<\v>, the entire
> > match will fail at the current position.
> > C<\V> is similar to C<\v>, except that when backtracking over C<\V>,
> > nothing left of the point C<\V> was matched cannot be part of the
> > match.
> This wording doesn't make sense to me. "... nothing left of the point
> \V was matched cannot be ..."
> I have no clue what \V does from that description. At a guess, if it is
> accurate, could it be...
> "... nothing to the left of the point \V was matched can be ..."
While its perhaps a waste to improve this given Larry's post,
hopefully this will clarify things.
=item \v, \V
Both C<\v> and C<\V> are new in perl5.10, and are shortcuts for
C<(*PRUNE)> and C<(*SKIP)>. See L<???>.
If the regular expression engines backtracks over C<\v>, the entire
match will fail at the current position.
C<\V> is similar to C<\v>, except that when backtracking over C<\V>,
all text consumed up to that point will be skipped before trying to reattempt
perl -Mre=debug -e "/just|another|perl|hacker/"