On 02/18/2011 01:56 PM, Paul Eggert wrote: > This suggests that we should use the name "stdint" for the > common case, and some other name for the rare case of > applications that need WINT_MIN etc. It'd be easy to > create a module "stdint-with-wchar" to do that, based > on the patch I already sent: simply have a dummy module > that depends on both stdint and wchar. But the name > "stdint-with-wchar" sounds rather ad hoc. And really > perhaps it is simpler just to say that if you need the > wchar stuff then use the wchar module too (which you'll > probably be doing anyway, so it's no big deal). This is > what stdlib already does with random_r.
Well, using <stdint.h> to get random_r is not standardized (we only
provided it for glibc compatibility, so it makes sense to make that
dependent on random_r), whereas the wchar_t stuff is standardized.
On the other hand, I agree that W{CHAR,INT}_{MAX,MIN} are unlikely to be
useful unless you are also using w{char,int}_t as defined by some other
header.
I'm perfectly fine with stdint being the simpler module, and
stdint+wchar being the complete replacement header. I don't even know
that we need a stdint-with-wchar module.
--
Eric Blake ebl...@redhat.com +1-801-349-2682
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
