's context that was interrupted when the signal was
delivered"), and specifically the words "context that was interrupted".
--
Geoff Clare <[EMAIL PROTECTED]>
The Open Group, Thames Tower, Station Road, Reading, RG1 1LX, England
object of type ".
I'll submit a defect report.
--
Geoff Clare <[EMAIL PROTECTED]>
The Open Group, Thames Tower, Station Road, Reading, RG1 1LX, England
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
Matthew Woehlke <[EMAIL PROTECTED]> wrote, on 30 Mar 2007:
>
> Geoff Clare wrote:
> >The code was just to illustrate the point that if it is possible for
> >the condition (var > SSIZE_MAX) to be true then the implementation
> >does not conform to the requirem
Paul Eggert <[EMAIL PROTECTED]> wrote, on 30 Mar 2007:
>
> Geoff Clare writes:
>
> > If the following code:
> >
> >ssize_t var;
> >var = SSIZE_MAX;
> >++var;
> >if (var > SSIZE_MAX)
> > puts("SSIZE_MAX wrong&quo
t; SSIZE_MAX)
puts("SSIZE_MAX wrong");
outputs "SSIZE_MAX wrong" on any implementation, then var is an object
of type ssize_t which was able to contain a value greater than
SSIZE_MAX, and therefore the implementation's definition of SSIZE_MAX
does not conform to th
