--- In [email protected], "Sheri" <sheri...@...> wrote:
>
> --- In [email protected], "entropyreduction"
> <alancampbelllists+yahoo@> wrote:
>
> The bsr_unicode and bsr_anycrlf options are kind of like the various
> newline_options, they override a library default. The newline options
> also have a interior pattern alternatives. I think you had to do
> something special for the plugin/external newline options.
So if library default is e.g. bsr_unicode, I need to turn that off in
presence of bsr_anycrlf...that makes sense. Will try.
There's a bunch of nasty code to do with what happens if match fails
but one of the multicharacter newline options is in force, then I have
to step one character and try again.
const DWORD CPcreAcess::M_NEWLINE_OPTIONS_ALL =
PCRE_NEWLINE_ANY | PCRE_NEWLINE_CRLF | PCRE_NEWLINE_CR |
PCRE_NEWLINE_LF | PCRE_NEWLINE_ANYCRLF;
...snip...
BOOL bIs2CharNL(IN INT iFlags)
{
iFlags &= M_NEWLINE_OPTIONS_ALL;
if (!iFlags)
return TRUE;
return iFlags == PCRE_NEWLINE_ANY || iFlags == PCRE_NEWLINE_CRLF ||
iFlags == PCRE_NEWLINE_ANYCRLF;
}
...snip...
if (m_iExecRet == PCRE_ERROR_NOMATCH)
{
.....
if (m_bJumpNL && m_iOffset + 1 < m_iLenSubject &&
m_pszSubject[m_iOffset] == '\r' &&
m_pszSubject[m_iOffset+1] == '\n')
m_iOffset++;
}
.....
Is any of that, or like it, relevant if bsr_unicode or bsr_anycrlf are
in force?
Can bsr_unicode or bsr_anycrlf and a PCRE_NEWLINE_* option be in foce
at once? I suppose so, I gather PCRE_BSR_* only has to to with
interpretation of \R?
> What about the javascript option? That still isn't working right
> either. Maybe you had better download the PCRE 7.8 source.
One thing at a time. Or two.
> I think the today's version it is not wrongly preserving what is
> intended to be a local variable, but something is still wrong.
Okay, try regexTest_090117.zip.
