perl6-language-regex  

Messages by Thread

• • Re: Perlstorm #0040 Richard Proctor
  • Re: Perlstorm #0040 Ilya Zakharevich
• RFC 274 (v1) Generalised Additions to Regexs Perl6 RFC Librarian
  • Re: RFC 274 (v1) Generalised Additions to Regexs Hugo
  • Re: RFC 274 (v1) Generalised Additions to Regexs Richard Proctor
  • Re: RFC 274 (v1) Generalised Additions to Regexs Hugo
• RFC 198 (v2) Boolean Regexes Perl6 RFC Librarian
  • RFC 198 (v2) Boolean Regexes Tom Christiansen
  • Re: RFC 198 (v2) Boolean Regexes Richard Proctor
• RFC 166 (v3) Alternative lists and quoting of things Perl6 RFC Librarian
  • Re: RFC 166 (v3) Alternative lists and quoting of things Hugo
• RFC 165 (v3) Allow Varibles in tr/// Perl6 RFC Librarian
• RFC 197 (v2) Numeric Value Ranges In Regular Expressions Perl6 RFC Librarian
• RFC 158 (v3) Regular Expression Special Variables Perl6 RFC Librarian
• RFC 158 (v2) Regular Expression Special Variables Perl6 RFC Librarian
• perl6-language-regex summary for 20000920 Hugo
  • Re: perl6-language-regex summary for 20000920 Richard Proctor
  • Re: RFC 197 (v1) Numeric Value Ranges In Regular Expressions David L. Nicol
  • Re: perl6-language-regex summary for 20000920 Ilya Zakharevich
• RFC 166 (v3) Allow Varibles in tr/// Perl6 RFC Librarian
• RFC 110 (v6) counting matches Perl6 RFC Librarian
  • Re: RFC 110 (v6) counting matches Bart Lateur
• \z vs \Z vs $ Tom Christiansen
  • Re: \z vs \Z vs $ Hugo
  • Re: \z vs \Z vs $ Bart Lateur
  • Re: \z vs \Z vs $ Tom Christiansen
  • Re: \z vs \Z vs $ Robert Mathews
  • Re: \z vs \Z vs $ Tom Christiansen
  • Re: \z vs \Z vs $ Bart Lateur
  • Re: \z vs \Z vs $ Tom Christiansen
  • Re: \z vs \Z vs $ Chaim Frenkel
  • Re: \z vs \Z vs $ Tom Christiansen
• RFC 93 (v3) Regex: Support for incremental pattern matching Perl6 RFC Librarian
• RFC 170 (v2) Generalize =~ to a special "apply-to" assignment operator Perl6 RFC Librarian
  • Re: RFC 170 (v2) Generalize =~ to a special "apply-to" assignment operator Simon Cozens
  • Re: RFC 170 (v2) Generalize =~ to a special "apply-to" assignment operator Nathan Wiger
• RFC 164 (v3) Replace =~, !~, m//, s///, and tr// with match(), subst(), and trade() Perl6 RFC Librarian
• RFC 166 (v2) Alternative lists and quoting of things Perl6 RFC Librarian
  • Re: RFC 166 (v2) Alternative lists and quoting of things Mark-Jason Dominus
  • Re: RFC 166 (v2) Alternative lists and quoting of things Richard Proctor
• Fwd: [Re: [FWP] Comic goodness] Michael G Schwern
• negative variable-length lookbehind example Hugo
• RFC 110 (v5) counting matches Perl6 RFC Librarian
• Generalised Additions to regexes Richard Proctor
• perl6-language-regex summary for 20000911 Mark-Jason Dominus
  • Re: perl6-language-regex summary for 20000911 Nathan Wiger
  • Re: perl6-language-regex summary for 20000911 David Corbin
  • Re: perl6-language-regex summary for 20000911 Paul Grzesina
• RFC 144 (v3) Behavior of empty regex should be simple Perl6 RFC Librarian
• special character to match a valid expression David L. Nicol
• RFC 165: Allow Variables in tr/// (post hugo) Richard Proctor
  • Re: RFC 165: Allow Variables in tr/// (post hugo) Mark-Jason Dominus
• RFC 166 (postHugo) Richard Proctor
  • Re: RFC 166 (postHugo) Nathan Torkington
• RFC 110 counting matches (post Hugo) Richard Proctor
  • Re: RFC 110 counting matches (post Hugo) Mark-Jason Dominus
• all regexp RFCs Hugo
  • Re: all regexp RFCs Hugo
• RFC 138 (v2) Eliminate =~ operator. Perl6 RFC Librarian
• Re: XML/HTML-specific ?< and ?> operators? (was Re: RFC 145 (alternate approach)) Damian Conway
• Re: XML/HTML-specific ?< and ?> operators? (was Re: RFC 145 (alternate approach)) Eric Roode
  • Re: XML/HTML-specific ?< and ?> operators? (was Re: RFC 145 (alternate approach)) Jarkko Hietaniemi
• RFC 198 (v1) Boolean Regexes Perl6 RFC Librarian
• What's in a Regex (was RFC 145) David Corbin
  • Re: What's in a Regex (was RFC 145) Jonathan Scott Duff
  • Re: What's in a Regex (was RFC 145) Tom Christiansen
  • Re: What's in a Regex (was RFC 145) Nathan Wiger
  • Re: What's in a Regex (was RFC 145) Tom Christiansen
  • Re: What's in a Regex (was RFC 145) Nathan Wiger
  • Re: What's in a Regex (was RFC 145) Tom Christiansen
  • Re: What's in a Regex (was RFC 145) Mark-Jason Dominus
  • Re: What's in a Regex (was RFC 145) Nathan Wiger
  • Re: What's in a Regex (was RFC 145) Tom Christiansen
  • Re: What's in a Regex (was RFC 145) mike mulligan
• RFC 197 (v1) Numberic Value Ranges In Regular Expressions Perl6 RFC Librarian
  • Re: RFC 197 (v1) Numberic Value Ranges In Regular Expressions Mark-Jason Dominus
• RFC 110 (v4) counting matches Perl6 RFC Librarian
• RFC 72 (v3) Variable-length lookbehind: the regexp engine should also go backward. Perl6 RFC Librarian
  • Re: RFC 72 (v3) Variable-length lookbehind: the regexp engine should also go backward. Bart Lateur
  • Re: RFC 72 (v3) Variable-length lookbehind: the regexp engine should also go backward. Peter Heslin
  • Re: RFC 72 (v3) Variable-length lookbehind: the regexp engine should also go backward. Bart Lateur
• perl6-language-regex summary for 20000831 Mark-Jason Dominus
  • Re: perl6-language-regex summary for 20000831 Richard Proctor
  • Re: perl6-language-regex summary for 20000831 Peter Heslin
  • Re: perl6-language-regex summary for 20000831 Mark-Jason Dominus
• RFC 164 (v2) Replace =~, !~, m//, s///, and tr// with match(), subst(), and trade() Perl6 RFC Librarian
  • Re: RFC 164 (v2) Replace =~, !~, m//, s///, and tr// with match(), subst(), and trade() Bart Lateur
  • Re: RFC 164 (v2) Replace =~, !~, m//, s///, and tr// with match(), subst(), and trade() Nathan Wiger
  • Re: RFC 164 (v2) Replace =~, !~, m//, s///, and tr// with match(), subst(), and trade() Bart Lateur
  • Re: RFC 164 (v2) Replace =~, !~, m//, s///, and tr// with match(), subst(), and trade() Nathan Wiger
• RFC 170 (v1) Generalize =~ to a special-purpose assignment operator Perl6 RFC Librarian
  • Re: RFC 170 (v1) Generalize =~ to a special-purpose assignment operator Nathan Wiger
  • Re: RFC 170 (v1) Generalize =~ to a special-purpose assignment operator Matthew Cline
  • Re: RFC 170 (v1) Generalize =~ to a special-purpose assignment operator Bart Lateur
• Re: RFC 165: Allow variables in a tr/// Stephen P. Potter
  • Re: RFC 165: Allow variables in a tr/// Mark-Jason Dominus
  • Re: RFC 165: Allow variables in a tr/// Nathan Wiger
  • Re: RFC 165: Allow variables in a tr/// Tom Christiansen
  • Re: RFC 165: Allow variables in a tr/// Nathan Wiger
  • Re: RFC 165: Allow variables in a tr/// Tom Christiansen
  • Re: RFC 165: Allow variables in a tr/// Mark-Jason Dominus
  • Re: RFC 165: Allow variables in a tr/// Tom Christiansen
  • Re: RFC 165: Allow variables in a tr/// Mark-Jason Dominus
  • Re: RFC 165: Allow variables in a tr/// Stephen P. Potter
  • Re: RFC 165: Allow variables in a tr/// Tom Christiansen
  • Re: RFC 165: Allow variables in a tr/// Stephen P. Potter
  • Re: RFC 165: Allow variables in a tr/// Piers Cawley
  • Re: RFC 165: Allow variables in a tr/// Bart Lateur
  • Re: RFC 165: Allow variables in a tr/// Tom Christiansen
  • Re: RFC 165: Allow variables in a tr/// Stephen P. Potter
  • Re: RFC 165: Allow variables in a tr/// Tom Christiansen
  • Re: RFC 165: Allow variables in a tr/// Eric Roode
• Overlapping RFCs 135 138 164 Mark-Jason Dominus
  • Re: Overlapping RFCs 135 138 164 Stephen P. Potter
  • Re: Overlapping RFCs 135 138 164 Nathan Wiger
  • Re: Overlapping RFCs 135 138 164 Steve Fink
  • Re: Overlapping RFCs 135 138 164 Tom Christiansen
  • Re: Overlapping RFCs 135 138 164 Tom Christiansen
  • Re: Overlapping RFCs 135 138 164 Uri Guttman
  • Re: Overlapping RFCs 135 138 164 Tom Christiansen
  • copying and s/// (was Re: Overlapping RFCs 135 138 164) Uri Guttman
  • Re: copying and s/// (was Re: Overlapping RFCs 135 138 164) Nathan Wiger
  • Re: copying and s/// (was Re: Overlapping RFCs 135 138 164) Brad Hughes
  • Re: copying and s/// (was Re: Overlapping RFCs 135 138 164) Mike Lambert
  • Re: copying and s/// (was Re: Overlapping RFCs 135 138 164) Nathan Wiger
  • Re: copying and s/// (was Re: Overlapping RFCs 135 138 164) Tom Christiansen
  • Re: copying and s/// (was Re: Overlapping RFCs 135 138 164) Tom Christiansen
  • Re: copying and s/// (was Re: Overlapping RFCs 135 138 164) Tom Christiansen
  • Re: copying and s/// (was Re: Overlapping RFCs 135 138 164) Tom Christiansen
  • Re: copying and s/// (was Re: Overlapping RFCs 135 138 164) David L. Nicol
  • Re: Overlapping RFCs 135 138 164 Steve Fink
  • Re: Overlapping RFCs 135 138 164 Tom Christiansen
  • Re: Overlapping RFCs 135 138 164 Nathan Wiger
• RFC 166 (disambiguator) Mark-Jason Dominus
  • Re: RFC 166 (disambiguator) Richard Proctor
• RFC 166 (does-not-match) Mark-Jason Dominus
  • Re: RFC 166 (does-not-match) Richard Proctor
  • Re: RFC 166 (does-not-match) Tom Christiansen
  • Re: RFC 166 (does-not-match) Mark-Jason Dominus
• RFC 110 (v3) counting matches Perl6 RFC Librarian
  • Re: RFC 110 (v3) counting matches Jonathan Scott Duff
  • Re: RFC 110 (v3) counting matches Tom Christiansen
  • Re: RFC 110 (v3) counting matches Jarkko Hietaniemi
  • Re: RFC 110 (v3) counting matches Jarkko Hietaniemi
  • Re: RFC 110 (v3) counting matches Mark-Jason Dominus
  • Re: RFC 110 (v3) counting matches Nathan Wiger
  • Re: RFC 110 (v3) counting matches Mark-Jason Dominus
  • Re: RFC 110 (v3) counting matches Damien Neil
  • Re: RFC 110 (v3) counting matches Mark-Jason Dominus
  • Re: RFC 110 (v3) counting matches Philip Newton
  • Re: RFC 110 (v3) counting matches Mark-Jason Dominus
  • Re: RFC 110 (v3) counting matches Bart Lateur
  • Re: RFC 110 (v3) counting matches Mark-Jason Dominus
  • $& and copying: rfc 158 (was Re: RFC 110 (v3) counting matches) Uri Guttman
  • Re: $& and copying: rfc 158 (was Re: RFC 110 (v3) counting matches) Mark-Jason Dominus
  • Re: $& and copying: rfc 158 (was Re: RFC 110 (v3) counting matches) Tom Christiansen
  • Re: $& and copying: rfc 158 (was Re: RFC 110 (v3) counting matches) Mark-Jason Dominus
  • Re: $& and copying: rfc 158 (was Re: RFC 110 (v3) counting matches) Mark-Jason Dominus
  • Re: RFC 110 (v3) counting matches Joe McMahon
  • Re: RFC 110 (v3) counting matches Tom Christiansen
  • Re: RFC 110 (v3) counting matches Jonathan Scott Duff
  • Re: RFC 110 (v3) counting matches Tom Christiansen
  • Re: RFC 110 (v3) counting matches Nathan Wiger
  • Re: RFC 110 (v3) counting matches Jonathan Scott Duff
  • Re: RFC 110 (v3) counting matches Nathan Wiger
  • Re: RFC 110 (v3) counting matches Tom Christiansen
  • Re: RFC 110 (v3) counting matches Nathan Wiger
  • Re: RFC 110 (v3) counting matches Bart Lateur
  • Re: RFC 110 (v3) counting matches Tom Christiansen
  • Re: RFC 110 (v3) counting matches Bart Lateur
  • Re: RFC 110 (v3) counting matches Tom Christiansen
  • Re: RFC 110 (v3) counting matches Bart Lateur
  • Re: RFC 110 (v3) counting matches Mark-Jason Dominus
  • Re: RFC 110 (v3) counting matches Tom Christiansen
  • Re: RFC 110 (v3) counting matches Tom Christiansen
  • Re: RFC 110 (v3) counting matches Tom Christiansen
  • Re: RFC 110 (v3) counting matches Nathan Wiger
  • Re: RFC 110 (v3) counting matches Tom Christiansen
  • Re: RFC 110 (v3) counting matches Mark-Jason Dominus
  • Re: RFC 110 (v3) counting matches Richard Proctor
  • Re: RFC 110 (v3) counting matches Philip Newton
  • Re: RFC 110 (v3) counting matches Mark-Jason Dominus
  • Re: RFC 110 (v3) counting matches Nathan Wiger
  • Re: RFC 110 (v3) counting matches Tom Christiansen
  • Re: RFC 110 (v3) counting matches Chaim Frenkel
  • Re: RFC 110 (v3) counting matches Jonathan Scott Duff
  • Re: RFC 110 (v3) counting matches Joe McMahon
  • Re: RFC 110 (v3) counting matches Jonathan Scott Duff
  • Re: RFC 110 (v3) counting matches Damien Neil
• RFC 72 (v1) The regexp engine should go backward as well as forward. Perl6 RFC Librarian
  • Re: RFC 72 (v2) The regexp engine should go backward as well as forward. mike mulligan
  • Re: RFC 72 (v2) The regexp engine should go backward as well as forward. Peter Heslin
  • Re: RFC 72 (v2) The regexp engine should go backward as well as forward. Mike Mulligan
  • Re: RFC 72 (v2) The regexp engine should go backward as well as forward. Hugo
  • Re: RFC 72 (v1) The regexp engine should go backward as well as forward. Mark-Jason Dominus
  • Re: RFC 72 (v1) The regexp engine should go backward as well as forward. mike mulligan
  • Re: RFC 72 (v1) The regexp engine should go backward as well as forward. Mark-Jason Dominus
  • Re: RFC 72 (v1) The regexp engine should go backward as well as forward. Tom Christiansen
  • Re: RFC 72 (v1) The regexp engine should go backward as well as forward. Peter Heslin
  • Re: RFC 72 (v3) Variable-length lookbehind: the regexp engine should also go backward. mike mulligan

• Earlier messages
• Later messages