The RFCs listed below are still listed as 'developing'. The deadline is
given as 1st October, but I'm not sure where the precise cutoff point
is - Nat, can you confirm?
As I understand it, RFCs not frozen by the deadline will be treated as
withdrawn. So please hurry.
If you make any substantial changes from the last published version of
the RFC, it would help if you could let the list have a last look at it
before submitting to the librarian to give us a chance to correct any
major new problems before they're writ in stone. I accept the short
timescales impose stringent limits on this.
I'm sorry I was unable to give an updated summary this week; if anyone
was waiting to discover specific information from it, please ask me.
Hugo
---
RFC 72: The regexp engine should go backward as well as forward. (Peter Heslin)
RFC 112: Assignment within a regex (Richard Proctor)
RFC 145: Brace-matching for Perl Regular Expressions (Eric Roode)
RFC 150: Extend regex syntax to provide for return of a hash of matched subpatterns
(Kevin Walker)
RFC 166: Alternative lists and quoting of things (Richard Proctor)
RFC 198: Boolean Regexes (Richard Proctor)
RFC 274: Generalised Additions to Regexs (Richard Proctor)
RFC 276: Localising Paren Counts in qr()s (Richard Proctor)
RFC 308: Ban Perl hooks into regexes (Simon Cozens)
RFC 316: Regex modifier for support of chunk processing and prefix matching (Bart
Lateur)
RFC 317: Access to optimisation information for regular expression (Hugo)
RFC 331: Consolidate the $1 and \1 notations (David Storrs)
RFC 332: Regex: Make /$/ equivalent to /\z/ under the '/s' modifier (Bart Lateur)
RFC 347: Remove long-deprecated $* (aka $MULTILINE_MATCHING) (Hugo)
RFC 348: Regex assertions in plain Perl code (Bart Lateur)
