Re^2: grep trouble

[LanX]

Are there any reasonable use cases/idioms for this feature?

If not, shouldn't there be a pragma to disable these edge cases?

[davido]

It could be a convenience for a switch with fall-through, or along similar (but more oddball lines), possibly an implementation of Duff's Device.

[LanX]

Thanks!

IMHO sounds like far less than 1‰ of all CPAN modules might rely on this.

---

UPDATE:

OK found another use-case, I just recently had the need in my ORG-Parser to distinguish the range delimiters and the range "body" with a flip-flop-operator, like for ORG's "BEGIN/END"-blocks.

This can be simplified (i.e. more DRY), if one has access to the last successful pattern:

  DB<114> for(0..99) {print if (/10/../20/ and not //)}
111213141516171819
  DB<115> for(0..99) {print if (/10/../20/)}
1011121314151617181920
  DB<116> for(0..99) {print if (/10/../20/ and //)}
1020

I think that's a more frequent application, I even slightly remember seeing it in Friedl's book.

But I'd rather prefer an explicit special varą, something like $PATTERN or $&& (in analogy to $MATCH resp. $&) .

1) an special var has the advantage that the regex itself can be accessed, e.g. printed.

update

for limitations see update in Re^2: Extract table from a block of text (updated)

[John M. Dlugosz]

It furthermore won't match at the same place twice, being a special case for a zero-length match. So // is just perfect for splitting a string into individual character, using split. I did that just yesterday.