Intro

Building upon the previous article, which explained how C language manipulates data through statements, this article continues to adhere to the principle of addressing the “why”. It begins with the end goal in mind, starting from the memory image required by the operating system to execute a program. From there, it works backwards to deduce the tasks that the compilation and linking subsystem must perform to bridge the gap between the source code and the final executable file.

Introduction

Last post describes how to model data by variables in C programming. When variables are ready, it’s time to design handy tools to use them.