EOF question..

[Chad]

Given something like:

#include <stdio.h>

int main(void) {
int c;

while( (c=getchar()) != EOF )
putchar(c);
return 0;
}
When I run and twice hit ctrl-d (indicating EOF on my system), I get
the following

cdalten@linux:~./ef
la la cdalten@linux:~>

Why does 'la ' get echoed back after the first EOF?

Chad

[Richard Tobin]

In article <11*********************@a75g2000cwd.googlegroups. com>,
Chad <cd*****@gmail.comwrote:

>Why does 'la ' get echoed back after the first EOF?

See the recent thread about EOF in this newsgroup. Short answer: your
first ctrl-D is not an end-of-file; it's a buffer flush
command. Ctrl-D is only sends end-of-file after a line break or
another ctrl-D. This is a feature of unix, not C itself.

-- Richard
--
"Consideration shall be given to the need for as many as 32 characters
in some alphabets" - X3.4, 1963.

[CBFalconer]

Chad wrote:

>
Given something like:

#include <stdio.h>
int main(void) {
int c;
while( (c=getchar()) != EOF )
putchar(c);
return 0;
}

When I run and twice hit ctrl-d (indicating EOF on my system),
I get the following

cdalten@linux:~./ef
la la cdalten@linux:~>

Why does 'la ' get echoed back after the first EOF?

Because the first "la" is not from your program, but from the input
system echoing the keys you typed. The second "la" is the programs
output. The input was buffered until either EOF or '\n' was
encountered, so your program saw nothing until that point.

--
"I conclude that there are two ways of constructing a software
design: One way is to make it so simple that there are obviously
no deficiencies and the other way is to make it so complicated
that there are no obvious deficiencies." -- C. A. R. Hoare