https://bugs.exim.org/show_bug.cgi?id=2285
--- Comment #7 from Markus Elfring <[email protected]> ---
(In reply to Philip Hazel from comment #6)
> Backporting to what?
Which PCRE2 variants are still supported?
> To PCRE1?
Maybe. - For any kind of long term support (by known software distributions)?
>> How much do you try to avoid duplicate (or redundant) checks in related
>> software?
>
> I'm sorry, I don't understand the question.
Other function implementations could have used extra checks because an API
property was not documented in preferred formats (besides the C source code) so
far.
> The ..._free() functions were an exception which is now rectified.
This update provides chances to improve the software situation for further
libraries and development tools, doesn't it?
> Several functions allow *some* of their arguments to be NULL, see for
> example, pcre2_match(),
> but I can't see how listing them separately is useful.
Do you distinguish usage categories for these functions?
Examples:
* Constructor
* Destructor
* Action
Is the âprobabilityâ for null pointers different in input parameters there?
(Could this detail be used for another bit of fine-tuning?)
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/pcre-dev
