Paul Eggert said: > Fine, but the point is that there's no portable way for an application > to determine whether adding 1 to a ssize_t variable will have "normal > execution" if the variable's value is SSIZE_MAX. This is regardless > of whether SSIZE_MAX is the maximum value representable in a ssize_t. > So I don't see the point of insisting on a guarantee that SSIZE_MAX > must be the maximum representable ssize_t value.
One reason is that it appears to fit in a naming scheme: in general, <T>_MAX is the maximum representable <T> or <T>_t value. Having SSIZE_MAX fit that schema but mean something different is, um, unfortunate. -- Clive D.W. Feather | Work: <[EMAIL PROTECTED]> | Tel: +44 20 8495 6138 Internet Expert | Home: <[EMAIL PROTECTED]> | Fax: +44 870 051 9937 Demon Internet | WWW: http://www.davros.org | Mobile: +44 7973 377646 THUS plc | |
