https://bugs.exim.org/show_bug.cgi?id=2285
--- Comment #6 from Philip Hazel <ph10@???> ---
(In reply to Markus Elfring from comment #5)
> This information is interesting. Does it eventually qualify for backporting
> in API descriptions?
Backporting to what? To PCRE1? That is now 3 years out-of-date.
> How much do you try to avoid duplicate (or redunant) checks in related
> software?
I'm sorry, I don't understand the question.
> The tolerance for null pointers in specific parameters could be expressed
> for each function.
When NULL is a valid value, it is usually mentioned. The ..._free() functions
were an exception which is now rectified.
> I would find it helpful to list these functions also in a corresponding
> documentation section.
Which functions? 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. (And it's hard enough already keeping all the documentation up-to-date,
without adding any more. :-)
--
You are receiving this mail because:
You are on the CC list for the bug.
