|
From: | Paul Eggert |
Subject: | Re: scratch_buffer: Document the exported API |
Date: | Sat, 6 Mar 2021 09:02:37 -0800 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 |
On 2/21/21 10:41 AM, Bruno Haible wrote:
it seems that some functions have a 'gl_' prefix and some don't. Does this matter? Maybe it does not matter because the contents of lib/malloc/dynarray.h is irrelevant and only lib/malloc/dynarray-skeleton.c matters?
The idea was that the gl_* symbols would not compete with the like-named __libc_* symbols when Gnulib dynarray is built under glibc. I don't recall the details about the competition, unfortunately.
Perhaps it'd work without the "#define __libc_dynarray_resize gl_dynarray_resize" etc. lines, because the two sets of __libc_*dynarray* functions would be in different C namespaces? But it might be confusing to debug.
[Prev in Thread] | Current Thread | [Next in Thread] |