Paul Eggert <[EMAIL PROTECTED]> wrote, on 30 Mar 2007: > > So I don't see the point of insisting on a guarantee that SSIZE_MAX > must be the maximum representable ssize_t value. What can a portable > application do with that guarantee that it couldn't do otherwise?
It can use SSIZE_MAX for the same kind of things as INT_MAX et al. are used, e.g. to check that an arithmetic operation will not overflow before performing it. -- Geoff Clare <[EMAIL PROTECTED]> The Open Group, Thames Tower, Station Road, Reading, RG1 1LX, England
