|
From: | Paul Eggert |
Subject: | Re: scratch_buffer.h, scratch_buffer_dupfree.c sync |
Date: | Thu, 3 Nov 2022 11:26:45 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.3 |
On 2022-11-03 04:03, Florian Weimer wrote:
I must say I was surprised to see dynarray and scratch_buffer end up in gnulib. I never intended them to escape this way from glibc.
They escaped from glibc because they're used by code shared with Gnulib (e.g., canonicalize.c).
The interfaces and their implementation are problematic in some ways, and I can't recommend them for general use.
Thanks for letting us know.What problems do you see with the interfaces, and are there efforts to come up with a better API? The need is there in GNU apps, each of which tends to roll its own code here.
[Prev in Thread] | Current Thread | [Next in Thread] |