Absolute C++ 6th Edition (Walter Savitch, Kenrick Mock)（Z-Library）

【One-Line Pitch】 A patient, example-driven introduction to C++ that treats programming as a craft of small, testable pieces—ideal for beginners with a little prior coding exposure and for self-learners who want a textbook that explains *why* as much as *how*. 【Book Arc】 - **Opening (~0%–10%)**: C++ basics—variables, expressions, assignment, console I/O with `cin`/`cout`, strings, and the case-sensitivity and declaration rules that trip up newcomers. - **Early (~10%–30%)**: Control flow and functions—Boolean expressions, short-circuit evaluation, `if`/`else`, loops, predefined and programmer-defined functions, scope rules, and the `exit` function. - **Middle (~30%–50%)**: Program design discipline—assertions and `#define NDEBUG`, stubs and driver programs for unit testing, then arrays: declaration, memory layout, indexed access, and partially filled arrays. - **Late (~50%+)**: The excerpts thin out here; later chapters presumably move into pointers, classes, inheritance, and the standard library, but the sampled material does not cover them in detail. - **Ending**: Not represented in the excerpts; the guide cannot map the closing chapters. 【Key Takeaways】 - **C++ is case-sensitive and declaration-before-use** (Opening): `count` and `COUNT` are distinct identifiers, and variables must be declared before use—foundational habits that prevent silent bugs. - **Short-circuit evaluation is a safety feature, not just an optimization** (Early): `(kids != 0) && ((pieces/kids) >= 2)` avoids division by zero because the second operand is never evaluated when the first is false. - **Integer division truncates** (Opening): `5/2` yields `2`, not `2.5`—a classic pitfall for anyone expecting fractional results. - **Functions are the unit of design and testing** (Middle): write driver programs to test each function in isolation, and use stubs for not-yet-written dependencies; this localizes bugs instead of hunting them across a whole program. - **Assertions are a debugging tool you can switch off** (Middle): `#define NDEBUG` before `#include <cassert>` disables all `assert` calls in a fully debugged program, removing runtime overhead. - **Arrays are contiguous and zero-indexed** (Middle): the computer stores the address of `a[0]` and computes other element addresses from it—understanding this explains why out-of-bounds access is dangerous. - **Partially filled arrays need a `numberUsed` argument** (Middle): functions that manipulate them must know how many slots are actually valid, and `fillArray` additionally needs the declared maximum size to avoid overfilling. - **Don't skimp on formal parameters** (Middle): passing `MAX_NUMBER_SCORES` explicitly makes `fillArray` reusable across programs rather than tied to one global constant. 【Reading Tips】 - **Deep-read Chapters 1–3** if you are new to C++: the variable, expression, and function material is the vocabulary everything else builds on. - **Skim the Self-Test answers** on a first pass, then return to them after attempting the exercises—they expose subtle rules like `2 < x < 3` always being true. - **Treat the Programming Projects as the real curriculum**: the craps simulation and child-height estimator force you to combine functions, loops, and I/O in ways the prose alone does not. - **Pause on the PITFALL and TIP boxes**: they encode the mistakes the authors have seen students make repeatedly, and they are cheap to read relative to the debugging time they save. - **Do not skip the testing chapter material** (stubs, drivers, assertions) even if it feels like overhead—it is the difference between a program that works and one you can fix. 【Coverage Limits】 The excerpts cover roughly the first half of the book (basics through arrays); later chapters on pointers, classes, inheritance, and the standard library are not represented, so this guide cannot summarize them. Chapter titles and percentages beyond ~50% are inferred only where the excerpts mention them.