--- In [email protected], "Sheri" <sheri...@...> wrote: > > --- In [email protected], "entropyreduction" > <alancampbelllists+yahoo@> wrote: > > > > While pouring over pcre.h and docs I find > > PCRE_NO_START_OPTIMIZE > > > > Don't think I've covered that? Should I have?
> Until now that would only be useful during callouts (which are disabled in > the plugin). But when marks are implemented that could change. So I would say > yes, implement PCRE_NO_START_OPTIMIZE as "slow" with no short version (but I > don't expect it to get much usage). Ok. Compile? Exec? Both? when executing pcre_dfa_exec I see the options PCRE_DFA_SHORTEST Return only the shortest match PCRE_DFA_RESTART Restart after a partial match Have I done them? Haven;t looked yet, but don;t ring a bell. pcre_dfa_exec dos say for extra data options: "the match_limit and match_limit_recursion fields are not used, For this matching function, the match_limit and match_limit_recursion fields are not used" Not sure if I made that sanity check. Will look and in same docs the mark field isn't shown in the struct or mentioned, so I imagine it too shouldn;t ever be allowed with dfa option? Does mark make sense with pcrematchcount? Probably not. Is PCRE_UCP both exec and compile option, or just one, if so which? docs say "PCRE must be built with UTF-8 support in order to use PCRE_UTF8 and PCRE_NO_UTF8_CHECK, and with UCP support if PCRE_UCP is used." Did you built with UCP and UTF-8 support?
