113 |
|
|
114 |
Run PrepareRelease and commit the files that it changes (by removing trailing |
Run PrepareRelease and commit the files that it changes (by removing trailing |
115 |
spaces). Then run "make distcheck" to create the tarballs and the zipball. |
spaces). Then run "make distcheck" to create the tarballs and the zipball. |
116 |
|
Double-check with "svn status", then create an SVN tagged copy: |
117 |
|
|
118 |
|
svn copy svn://vcs.exim.org/pcre/code/trunk \ |
119 |
|
svn://vcs.exim.org/pcre/code/tags/pcre-7.x |
120 |
|
|
121 |
Don't forget to update Freshmeat when the new release is out, and to tell |
Don't forget to update Freshmeat when the new release is out, and to tell |
122 |
webmaster@pcre.org and the mailing list. |
webmaster@pcre.org and the mailing list. |
221 |
to switch this dynamically. It would have to be specified when PCRE was |
to switch this dynamically. It would have to be specified when PCRE was |
222 |
compiled. PCRE would then call a function every time it wanted a character. |
compiled. PCRE would then call a function every time it wanted a character. |
223 |
|
|
|
. There are new (*PRUNE) facilities in Perl 5.10, some of which it might be |
|
|
relatively easy to implement. |
|
|
|
|
224 |
. Wild thought: the ability to compile from PCRE's internal byte code to a real |
. Wild thought: the ability to compile from PCRE's internal byte code to a real |
225 |
FSM and a very fast (third) matcher to process the result. There would be |
FSM and a very fast (third) matcher to process the result. There would be |
226 |
even more restrictions than for pcre_dfa_exec(), however. This is not easy. |
even more restrictions than for pcre_dfa_exec(), however. This is not easy. |
234 |
|
|
235 |
. Someone suggested --disable-callout to save code space when callouts are |
. Someone suggested --disable-callout to save code space when callouts are |
236 |
never wanted. This seems rather marginal. |
never wanted. This seems rather marginal. |
237 |
|
|
238 |
. "Cut" as described in Jeffrey Friedl's book, p364: \v and \V. The definitions |
. Check names that consist entirely of digits: PCRE allows, but do Perl and |
239 |
aren't yet clear enough for me. \v flushes saved states so that no |
Python, etc? |
|
backtracking to anything earlier can happen; \V says "no more bumpalong", but |
|
|
does it fail the current match? As described in the book, these aren't really |
|
|
"cut" as in Prolog, are they? NOTE: (a) PCRE once had "cut", but it was |
|
|
removed when atomic groups were introduced. (b) Perl 5.10 has some (*PRUNE) |
|
|
features -- |
|
|
|
|
|
. These are the Perl 5.10 backtracking control features (all of which are |
|
|
described as "experimental" -- some of them "very experimental") that it |
|
|
might be easy to add to PCRE. They all succeed when encountered, but act as |
|
|
follows when backtracking: |
|
|
|
|
|
(*PRUNE) fail this match attempt, but still bumpalong |
|
|
(*SKIP) fail this match attempt, bumpalong to current match point |
|
|
(*THEN) fail this branch, try next branch at same level or fail if none |
|
|
(*COMMIT) fail this match attempt, suppress bumpalong |
|
|
(*FAIL) fail and backtrack (same as (?!) and that can be optimized) |
|
|
(*F) synonym for (*FAIL) |
|
|
(*ACCEPT) behave as if end of pattern reached ("very experimental") |
|
|
|
|
|
Some of these can have arguments (*PRUNE:NAME) but I'm not sure whether they |
|
|
make sense in the PCRE context. |
|
240 |
|
|
241 |
Philip Hazel |
Philip Hazel |
242 |
Email local part: ph10 |
Email local part: ph10 |
243 |
Email domain: cam.ac.uk |
Email domain: cam.ac.uk |
244 |
Last updated: 13 June 2007 |
Last updated: 09 August 2007 |