[pcre-dev] [Bug 1830] pcre2posix defines the same names as P…

Top Page

Reply to this message
Author: admin
Date:  
To: pcre-dev
Old-Topics: [pcre-dev] [Bug 1830] New: pcre2posix defines the same names as POSIX
Subject: [pcre-dev] [Bug 1830] pcre2posix defines the same names as POSIX
https://bugs.exim.org/show_bug.cgi?id=1830

--- Comment #21 from Petr Pisar <ppisar@???> ---
The forthcoming 10.33 defines and declares both functions. That's great but it
does not fix the issue completely. An application must start using the prefixed
function to resolve the issue.

My patch, that is built on top of the forthcoming 10.33, turns the non-prefixed
_declarations_ into macros. It keeps the non-prefixed definitions.

This way Python continue working because the dynamic library will contain the
non-prefixed function. However, and this the goal of my patch, after rebuilding
Python, Python will use prefixed functions. And exactly since this point Python
won't crash anymore.

This is what my PCRE2 patch does.

My PCRE1 patch combines your PCRE2 patch from the forthcoming 10.33 with my
PCRE2 patch.

If you feel uncomfortable with applying my patches, fine. I just want to point
that your 10.33 code as it is now does not provide a complete fix. But you
probably know that because 10.33 also documents that an application must be
changed to utilize the new prefixed functions.

--
You are receiving this mail because:
You are on the CC list for the bug.