[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

Petr Pisar <ppisar@???> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ppisar@???


--- Comment #14 from Petr Pisar <ppisar@???> ---
Created attachment 1167
--> https://bugs.exim.org/attachment.cgi?id=1167&action=edit
Declare POSIX regex function names as macros to PCRE functions

The committed patch fixes the issue only if an application redefines the
function names as described in README or call the prefixed functions directly.
But why making it more difficult, if the redefinition can be implemented in
perl2posix.h that must be included at any rate?

At first, I thought there is some benefit I cannot see and that dictates the
current status. But then I made some tests
<https://bugzilla.redhat.com/show_bug.cgi?id=1667614#c2> and came to a
conclusion that if an application includes pcre2posix.h, the only correct
operation mode is using PCRE's implementation.

Thus please consider this attached patch that simply by including
<pcre2posix.h> makes applications sure bad things won't happen.

(I still struggle with reproducing the bad things, but since plenty of Linux
distributions contain a similar hack and there are suffering applications
<https://github.com/cyrusimap/cyrus-imapd/issues/2629>, I cannot pretend that
the issue does not exist.)

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