Exercise 8-4. The standard library function int fseek(FILE *fp, long offset, int origin) is identical to lseek except that fp is a file pointer instead of a file descriptor and the return value is an int status, not a position. Write fseek. Make sure that your fseek coordinates properly with the buffering done for the …
Exercise 8-3. Design and write _flushbuf, fflush, and fclose. Exercise 8-2 built the read half of a miniature stdio; this one builds the write half. The design mirrors getc/_fillbuf: putc is a macro that drops characters into a buffer, and only when the buffer fills does it call the real function — _flushbuf — which …
Exercise 8-2. Rewrite fopen and _fillbuf with fields instead of explicit bit operations. Compare code size and execution speed. Chapter 8 sketches a miniature version of the standard I/O library: a FILE structure holding a buffer, a count, a position pointer, and a set of status flags. In the book the flags live in one …
Exercise 8-1. Rewrite the program cat of Chapter 7 using read, write, open and close instead of their standard library equivalents. Perform experiments to determine the relative speeds of the two versions. The Chapter 7 cat goes through the standard library — getchar and putchar — which quietly buffer I/O for you. This exercise drops …
Big day for this site: C Program Examples is live on Product Hunt today. If you’ve found the tutorials, quizzes, or K&R solutions here useful, dropping by the launch page to say hello (or leave honest feedback) would mean a lot — it’s a 24-hour window, and every comment helps other C learners discover the …
Memory management is where C interviews get serious. Pointers test syntax — memory questions test whether you can be trusted with a production codebase. This page collects 25 real C memory management interview questions with clear answers and tested, compilable code: stack vs heap, the malloc family, leaks, dangling pointers, double free, struct padding, and …