Re: tolower()/islower() and char

To: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
Subject: Re: tolower()/islower() and char
From: Martin Husemann <martin%duskware.de@localhost>
Date: Thu, 14 Jan 2021 12:52:06 +0100

On Thu, Jan 14, 2021 at 12:28:57PM +0100, Manuel Bouyer wrote:
> Does the standard explicitely state that the value should either be
> EOF or >= 0 ?

Yes, Section 7.4 paragrah 1 second sentence (ISO C 2018):

> In all cases the argument is an int, the value of which shall be
> representable as an unsigned char or shall equal the value of the
> macro EOF.  If the argument has any other value, the behavior is
> undefined.

Martin

Follow-Ups:
- Re: tolower()/islower() and char
  - From: Manuel Bouyer

References:
- tolower()/islower() and char
  - From: Manuel Bouyer
- Re: tolower()/islower() and char
  - From: Martin Husemann
- Re: tolower()/islower() and char
  - From: Manuel Bouyer

Prev by Date: Re: tolower()/islower() and char
Next by Date: Re: Waiting for Randot (or: nia and maya were right and I was wrong)
Previous by Thread: Re: tolower()/islower() and char
Next by Thread: Re: tolower()/islower() and char
Indexes:

Home | Main Index | Thread Index | Old Index