The desired program output is as follows:Code:#include <stdio.h> #define WAIT system("sleep 2") main() { printf("Helllo\n"); WAIT; }
1)Program prints the "Hello" msg
2)It halts for 2 seconds
3)It finally exits
But if we write something like:
(\n character ommited)Code:printf("Hello"); WAIT;
then the output changes:the program first halts and
then prints the msg.
Is there anybody out there that happens to know why this happens?
Does that still happen if you #include <stdlib.h>
R.I.P C89
The program continues to behave the same.
oh by the way i am using the gcc compiler in a Unix system.
Okay, what about...
Code:... printf("string"); fflush(stdout); WAIT; ...
R.I.P C89
The reason it pauses and then displays the text when you remove the newline is because the system hasn't flushed the output buffer.
The system always tries to be as effiecent as possible. As such it doesn't write characters one at a time to the screen. It waits till it has a bunch of stuff to write.
Normally if you do something like printf("hello"); and then wait for user input it will display find but by putting the sleep in the mix you are causing the system to be busy and as such it won't display the text.
Putting a newline tells the system to flush the output buffer. You can also use the fflush(stdout); like c99 suggested.
Hope this helps.
That's quite interesting to know. Thanks for the extra info.Originally posted by Thantos
Putting a newline tells the system to flush the output buffer.
R.I.P C89
Something I found interesting for this code:
When using a function like system(), YMMV (Your Mileage May Vary). For Windows systems, Borland bcc exhibits the same behavior with or without the \n. Note that Windows version of gcc (installed with Cygwin) acts like the UNIX gcc: behavior with \n is not same as without \n.
(Note: with Borland, you have to #include <stdlib.h> to use the system() function.)
Why do I find this interesting?
Many times people use tried-and-true pieces of code when changing to a new programming environment and find that things don't work the way they used to.
Last edited by Dave Evans; 03-06-2004 at 10:11 AM.
system() calls aren't portable, either. An example using clock() (in time.h):
Code:void wait(unsigned timeout) { timeout += clock(); while(clock() < timeout) continue; }
Code:#include <cmath> #include <complex> bool euler_flip(bool value) { return std::pow ( std::complex<float>(std::exp(1.0)), std::complex<float>(0, 1) * std::complex<float>(std::atan(1.0) *(1 << (value + 2))) ).real() < 0; }
>>Note: with Borland, you have to #include <stdlib.h> to use the system() function.
That's because the Standard says system() lives in stdlib.h, so you should always #include that library.
When all else fails, read the instructions.
If you're posting code, use code tags: [code] /* insert code here */ [/code]
Gee,guys,thanks for all the help!!
I mean,i can't believe that so many people would like to comment my piece of code,and help me understand why this output occurs.Really appreciated,fellows!
On last thing though:does anyone know where i can find more info about the fflush function and the way the output buffer works?THe books i have about C don't say much about this.
try man fflush
and
man 3 fflush
Not a lot of info, but might get you started.
