Eric Blake <[EMAIL PROTECTED]> writes: > I'm seeking backup from those more knowledgeable about the C > and POSIX standards as to whether NSK is allowed to define SSIZE_MAX to > something smaller than what the underlying type can hold,
Yes, that's my understanding. To back this up, <http://www.opengroup.org/susv3/basedefs/sys/types.h.html> says "The type ssize_t shall be capable of storing values at least in the range [-1, {SSIZE_MAX}]" which has the clear implication that ssize_t might be able to store values greater than SSIZE_MAX. > whether it is worth auditing gnulib to find any places that have > previously assumed that SSIZE_MAX is ((1<<(sizeof(ssize_t)*CHAR_BIT - > 2))-1)*2+1. My kneejerk reaction is that it's not worth _my_ time but it might be worth _Matthew's_....
