Paul Eggert wrote: > xalloc-die, in contrast, doesn't have a substitute in gnulib; if you > don't use gnulib xalloc-die but some gnulib code needs it, you have to > implement it yourself (that is, the same API will not work unless you > implement it). This seems to be what --avoid is for.
Yes, exactly. > unlocked-io can always be omitted Yes. But if you ever want to go back from #if USE_UNLOCKED_IO # include "unlocked-io.h" #endif to a simple #include "unlocked-io.h" then --avoid will do the trick as well. Regarding xalloc-die, I propose this patch. Bruno *** modules/xalloc 21 Mar 2005 22:07:25 -0000 1.15 --- modules/xalloc 14 Jul 2005 16:22:55 -0000 *************** *** 7,12 **** --- 7,13 ---- m4/xalloc.m4 Depends-on: + xalloc-die configure.ac: gl_XALLOC *** modules/xvasprintf 25 Mar 2005 16:58:46 -0000 1.3 --- modules/xvasprintf 14 Jul 2005 16:22:55 -0000 *************** *** 9,14 **** --- 9,15 ---- Depends-on: vasprintf + xalloc-die configure.ac: _______________________________________________ bug-gnulib mailing list bug-gnulib@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnulib