Re: [pcre-dev] PCRE2 first Release Candidate

Hello,

I noticed an issue so far with CMAKE under Windows and Visual Studio 2013:

PCRE2_BUILD_PCRE2_8 = ON works, but switching on PCRE2_BUILD_PCRE2_16
and PCRE2_BUILD_PCRE2_32, too, causes function prototype conflicts (same
name exported/defined several times).

I also noticed that there is still an option PCRE2_SUPPORT_BSR_ANYCRLF
that is separate from PCRE2_SUPPORT_UNICODE.

Isn't this inconsistent considering the following decision? (If you
extend normal character classes to Unicode why not linebreaks, too? That
it is disabled by default is a consistent default, though.)
> 2. Note that --enable-utf and --enable-ucp have been amalgamated
> into --enable-unicode, and this is now the default.

Regards, Maël Hörz