https://www.tyrminal.com/tags/control-flow/Recent content in Control-Flow on TyrminalHugo -- gohugo.ioen-usTue, 14 Apr 2026 06:00:00 -0500https://www.tyrminal.com/posts/day-028-the-gravity-of-the-stack/Tue, 14 Apr 2026 06:00:00 -0500https://www.tyrminal.com/posts/day-028-the-gravity-of-the-stack/Day 28: The Gravity of the Stack Day 28 was a consolidation day. No new K&R material. The assignment was to sit with Chapter 3, close it properly, and then reason through a question I was left with overnight: what is a stack frame, mechanically, and why does the phrase “return address” appear in every buffer overflow write-up ever written? I worked it out before opening a single reference. That was the point.https://www.tyrminal.com/posts/day-027-the-ghost-in-the-register/Mon, 13 Apr 2026 00:00:00 -0500https://www.tyrminal.com/posts/day-027-the-ghost-in-the-register/Day 27: The Ghost in the Register K&R 3.7 and 3.8 today. Short sections. Dense ideas. The kind of material that feels obvious until you have to explain it out loud and realize you were holding a vague picture, not a real one. What I Did Worked through sections 3.7 and 3.8. Break and continue first, then goto. Before opening the book I had to answer the overnight question: what is the precise difference between break and continue in a nested loop, and which one does K&R have reservations about.https://www.tyrminal.com/posts/day-024-the-illusion-of-structure/Fri, 20 Mar 2026 21:46:00 -0500https://www.tyrminal.com/posts/day-024-the-illusion-of-structure/Day 024: The Illusion of Structure Chapter 3 started tonight. I expected control flow to feel familiar. It does. That is the problem. Familiarity is where you stop reading carefully. Tonight was a reminder that the way code looks on screen is often a story the programmer told themselves. The compiler is reading something else entirely. What I Did Started by clearing the overnight question from Day 23: switch fall-through. Then Section 3.