> We're upgraded to the latest PCRE now (thanks for Cliff to fixing the > Win32 build).
Thanks. > I checked with the PCRE maintainer and learned that the next release is > several months away. In the meantime, that leaves me with two options > for speeding up ap_regexec(): > > * Commit a change to the PCRE regexec() function (the same change > that I've submitted for the next release of PCRE) into the Apache > copy of PCRE for now. Yeah, do that, but surround it with comments saying that it is a change that has been submitted to the maintainer. > * Or change ap_regexec() to bypass regexec() and call the PCRE "native" > regexp exec function directly. (The PCRE regexec() is a thin wrapper > around pcre_exec(), so this shouldn't be difficult.) Ummm, do we always use our PCRE for the regexec library? I was under the impression that it is configurable. ....Roy
