Re: enforcing the use of string.h related modules

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Bruno Haible on 1/27/2007 8:10 AM:
> 
> Most of us are developing on sane systems with few broken or missing
> functions. If, for example, someone uses the 'string' module and stpcpy(),
> he will not get a warning: /usr/include/string.h declares stpcpy(), and
> glibc implements it. So the programmer is unaware of the portability
> problem. Here is a proposed patch, that leads to a link error if someone
> uses stpcpy() without the 'stpcpy' module (assuming the 'string' module
> is present - which is quite likely since so much depends on it).

Sounds like a great idea to me.  I guess the alternative would be making
stpcpy.c part of the string module, and removing the stpcpy module
altogether (and likewise for the other affected modules), but that has
more churn on existing gnulib users.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFu8no84KuGfSFAYARApTmAJ9WJTorX7J1TjB6ugatIoLVwUNl8wCfWY/k
qHhxo7utYRpPmM31PbWf0+A=
=IkEN
-----END PGP SIGNATURE-----