https://bugs.exim.org/show_bug.cgi?id=1679
--- Comment #3 from henrik.hank@??? ---
Would there arrive confusion about memory responsibility if just new strings
were allocated and be returned when a capture string is modified, or
unacceptable work to be done on a regular basis for a feature seldomly used?
Isn't there an elegant way to overcome this? What about letting an API user
opt-in for freeing memory/destroying handles after using a find or replace
function?
Otherwise, is there another possibility to accomplish find-and-replace
according to a list without being forced to apply many find-and-replace actions
one after the other?
--
You are receiving this mail because:
You are on the CC list for the bug.
