Learning C By Example (Agus Kurniawan)（Z-Library）

# Learning C By Example — Reading Guide ## 【One-Line Pitch】 A hands-on, code-first introduction to C programming that walks beginners from compiler setup through threading, databases, and socket programming — ideal for self-learners who want to see working examples rather than lengthy theory. ## 【Book Arc】 - **Opening (~0%–6%)**: Environment setup across Linux, Windows, and Mac, including GCC installation, editor choices, and the classic Hello World — establishes the compile-and-run workflow used throughout. - **Early (~6%–18%)**: Core language fundamentals — variables, arithmetic, logical operators, decision-making with if/switch, loops, structs, and arrays — building a solid syntax foundation. - **Early (~18%–29%)**: Pointer concepts and dynamic memory allocation, followed by function creation, array parameters, and pointer-based function arguments like swap() — the conceptual heart of C. - **Middle (~29%–41%)**: I/O operations including safe input handling with fgets(), string manipulation with strcat() and strlen(), and building reusable C libraries (static and shared). - **Middle (~41%–59%)**: Threading with pthreads — creating threads, obtaining thread IDs, termination strategies, joining, mutex synchronization, and condition variables for signaling. - **Late (~59%–100%)**: Database programming and socket communication (server/client models) — applying earlier concepts to real-world system programming scenarios. ## 【Key Takeaways】 - **Environment setup is the first hurdle** (Early): The book provides platform-specific GCC installation steps for Linux, Windows (Cygwin), and Mac (Xcode), plus editor recommendations — get this right and everything else flows smoothly. - **Semicolons and type discipline matter** (Early): Every statement ends with `;`, and assigning incompatible types (like a string to an int) triggers compiler warnings — the book uses these errors as teaching moments. - **Pointers are memory addresses with power** (Early): Using `&` to get addresses and `*` to dereference, you can build dynamic arrays and pass values by reference — essential for understanding C's memory model. - **Functions with array parameters need explicit sizes** (Early): Unlike higher-level languages, C functions must receive array length as a separate argument, as shown in the mean() calculation example. - **gets() is unsafe — use fgets()** (Middle): The book explicitly demonstrates the danger of gets() and shows fgets() with length limits as the safer alternative for reading text input. - **Building libraries requires header files** (Middle): Creating a static library involves compiling source to object files, creating a header with extern declarations, and linking with `-I` and `-L` flags — a practical introduction to code reuse. - **Thread synchronization prevents race conditions** (Middle): Mutex locks protect shared variables like total_finished_jobs, while condition variables provide signaling and broadcasting mechanisms for more complex coordination. ## 【Reading Tips】 - **Skim the environment setup** (~0%–6%) if you already have GCC working — just note the compile commands (`gcc -o output source.c`) used consistently throughout. - **Deep-read the pointer and function chapters** (~18%–29%) — these are the conceptual foundation for everything later, especially the swap() example and dynamic array implementation. - **Pay attention to the library chapter** (~35%–41%) — the distinction between static (.a) and shared (.so) libraries is practical knowledge you'll reuse in real projects. - **The threading chapter is dense** (~41%–59%) — work through the mutex and condition variable examples slowly, as they demonstrate patterns you'll encounter in system programming. - **Each chapter follows the same pattern**: code sample → save to file → compile → run → observe output. Replicate this workflow yourself rather than just reading. ## 【Coverage Limits】 This guide covers the first ~59% of the book in detail (through threading). The database programming and socket programming chapters appear in the table of contents but their content is not covered in the available excerpts. ##