Current-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: isspace() behaviour
On Wed, Dec 18, 2024 at 11:33:46 +0100, Christoph Badura wrote:
> > (That value was used in the program as "an EOF occured when that char
> > was read".)
>
> "an EOF occured when that char was read" leaves me stumped.
> Clearly, if you are able to read a char, you weren't at EOF and if you
> were at EOF you wouldn't be able to read a char. That's how Unix has
> worked forever.
I think it means to say that an attempt to read a char was made, that
attempt failed with EOF, but that "EOF" value was passed to a ctype
macro.
-uwe
Home |
Main Index |
Thread Index |
Old Index