Re: return'ing a struct and trap representations

>> Should be: for integer and pointer types there are _no_ "trap >> representations". > > I don't think that is guaranteed by C99. That's correct. As I recall, only unsigned char objects are guaranteed to be free of trap representations. > Certainly the practical value of this for gnulib is que

Re: getopt error message wording

[EMAIL PROTECTED] (Eric Blake) writes: > Is it worth updating the getopt > module to depend on posixver and avoid this term except when > _POSIX2_VERSION is set to the older version of POSIX? I'd say "no". Such an update would affect behavior only if POSIXLY_CORRECT is set, right? Normally it's

getopt error message wording

Currently, getopt bases its decision of whether to print "illegal option" or "invalid option" solely on the presence of POSIXLY_CORRECT, but POSIX 2001 relaxed the requirements so that the error message no longer need use the term "illegal". Is it worth updating the getopt module to depend on posi