But the facility of obstacks is in glibc for 10 years now. This means,
it will get hard for you to convince the glibc maintainers.
I have improved my patch and sent it to libc-alpha. Let's wait the
result. Thank you.
> The third one requires more libraries to be linked with and I do not
want
Thank you for the suggestions.
> Below is my patch to obstack
gnulib provides for obstack the same API as glibc. It makes no sense for
gnulib to provide a variant of obstack that has features that glibc does
not have.
Therefore the right place to post your patch is either the libc-alpha
AT sou
I have trouble using obstacks with my threaded server, since obstack's
error handling is not thread safe. It provides a user defined
function `obstack_alloc_failed_handler' to signal errors when
allocation fails, and this function can call longjmp instead of
exiting. But I can only call longjmp
Hello,
I have some questions on the argp implementation. Please take a look
at them. Thanks.
1. On ARGP_KEY_ARGS
The document of this macro, in the libc document, says:
`ARGP_KEY_ARGS'
If a parser function returns `ARGP_ERR_UNKNOWN' for
`ARGP_KEY_ARG', it is immediately called again
