Basics.Of.Compile.Design.2008
1.1 What is a compiler? 1.2 The phases of a compiler 1.3 Interpreters 1.4 Why learn about compilers? 1.5 The structure of this book ......
1.1 What is a compiler? 1.2 The phases of a compiler 1.3 Interpreters 1.4 Why learn about compilers? 1.5 The structure of this book ......
Hi, there. Thank you for reading my book, Exploring C++. My name is Ray, and I’ll be your author today. And tomorrow. And the day after that. We’ll be together for quite a while, so why don’t you pull up a chair and get comfortable. My job is to help you learn C++. To do that, I have written a series of lessons, called explorations. Each exploration is an interactive exercise that helps you learn C++ one step at a time. Your job is to complete the explorations, and in so doing, learn C++. No doubt you have already leafed through the book a little bit. If not, do so now. Notice that this book is different from most books. Most programming books are little more than written lectures. The author tells you stuff and expects you to read the stuff, learn it, and understand it. This book is different. I don’t see much point in lecturing at you. That’s not how people learn best. You learn programming by reading, modifying, and writing programs. To that end, I’ve organized this book so that you spend as much time as possible reading, modifying, and writing programs.
Chapter 1 Memory Management Mechanisms Chapter 2 Memory Management Policies Chapter 3 High-Level Services Chapter 4 Manual Memory Management Chapter 5 Automatic Memory Management Chapter 6 Miscellaneous Topics