question on k&r problem

[ioil]

Hello, this question arose when testing the answer to one of k&r's exercises.

The idea is to count blanks, tabs, and newlines before EOF is reached.

insert

#include <stdio.h>

main()
{
	int c;
	int b = 0;
	int t = 0;
	int n = 0;

	while ((c = getchar()) != EOF) {
		if (c == ' ')
			b++;
		if (c == '\t')
			t++;
		if (c == '\n')
			n++;
	}

	printf("Blanks : %d\nTabs : %d\nNewlines : %d\n", b, t, n);
}

Starting the program then pressing CTRL-C yields :


C:\>counter.exe

Blanks : 0
^C
C:\>


So the process, after it gets the SIGINT signal, breaks it out of the loop and prints part of the printf statement. Why only part . . . wondering if anyone knows what is going on inside the computer, thanks.

[msh]

EOF is Ctrl-Z in Windows.

It's int main() according to the latest C standard (C99), int main( void ) if you want to be explicit. This change also requires that you have a return statement at the end of main().

[laserlight]

So the process, after it gets the SIGINT signal, breaks it out of the loop and prints part of the printf statement. Why only part . . . wondering if anyone knows what is going on inside the computer, thanks.

I cannot seem to duplicate your problem. That said, it may make more sense to simulate EOF with CTRL+D or CTRL+Z rather than use CTRL+C.

It's int main() according to the latest C standard (C99), int main( void ) if you want to be explicit. This change also requires that you have a return statement at the end of main().

Yes, though a related change does not require one to have a return statement at the end of the main function.

[quzah]

CTRL+C typically terminates the currently running application (assuming you're running through the command prompt/shell), which is not the same as sending EOF.


Quzah.

[Babkockdood]

CTRL-C terminates the program. CTRL-Z prints EOF.