CODEWITHSUNDEEP
cgcc
pdssn
pdssn

Reputation: 225

Why I couldnt work with the gcc compiler without '\n' in printf?

I have written a printf() statement like below:

printf("hello\n");

this works fine when built using Linux' gcc compiler. However if I write

printf("hello");

the print doesn't appear on the screen. There is some buffering mechanism it seems? Can anybody give me more information on this?

Upvotes: 3

Views: 1486

Answers (3)

gbjbaanb
gbjbaanb

Reputation: 52679

Try the fflush() call. Typically writing to a screen or file is very expensive, so the data is buffered until it needs to be written. A \n usually is enough to do the trick (buffers generally store only 1 line at a time anyway), but if you need to flush the buffer - use that flush call.

Upvotes: 14

ShoeLace
ShoeLace

Reputation: 3576

I posted here about unbuffered IO on windows..

but its a standard c-call to setvbuf

setvbuf(stdout, (char *)NULL, _IONBF, 0); //unbuffered stdout

Upvotes: 2

Andre Miller
Andre Miller

Reputation: 15493

Even if buffering isn't a problem, if you don't print the newline your shell's prompt might be clobbering the output.

I'm not sure in which environment you are running this, but if you are for example using gcc in a unix shell and at the end of your program do printf("hello") it won't print a newline before your shells prompt is displayed. The prompt will be printed on that same line, sometimes overwriting the entire line depending on kind of prompt you have set up.

Upvotes: 7

Related Questions