jim mcnamara

Canonical vs non-cononical terminal I/O?

The setbuf function in stdio is defined to be able to turn off/on buffering. Subsequent fprintf calls are affected. In most implementations, you must call setbuf before any I/O to the terminal occurs.

Windows and unix have terminal I/O libraries that change terminal characteristics as well.

Fall Back Son

edit: sorry, I had read all of the posts in here except a couple newer ones and I didn't realize the guy above me already mentioned setbuf.

my advice is to go to linux and type in man stdout.. it gives a lot of useful information, including (some) of what has been said here. If you want to, you can change the buffering mode (for lack of a better term) using setbuf. I haven't played with it, so I'm not sure how advisable it is to do so. Maybe one of these guys wouldn't mind giving some advice on how to use it properly.

Harakim

Use the write() function if you are in a posix environment. I have never done low-level c in windows, but every other environment I have worked in has it.

write( STDOUT_FILENO, message, strlen(message) );

I suppose this is too late to help with your assignment, but not to late to learn something.


search for:
"c write function"
(without quotes) in google if you would like to know more.

rsnd

for windows you can get output handle by GetStdHandle(STD_OUTPUT_HANDLE); (kernel32.lib) You can use native windows file write functions to write to it.

__________________
Spread your wings and fly! Chicken!