C is a general-purpose, procedural programming language designed to let programmers write structured programs while still giving them close control over memory and machine-level operations.

C source file (.c)
      ↓
Preprocessing
      ↓
C source after directives are handled
      ↓
Compilation
      ↓
Assembly / object code
      ↓
Linking with required libraries and object files
      ↓
Executable program
      ↓
Operating system loads it
      ↓
Running process

C was developed at Bell Labs in the early 1970s, primarily by Dennis Ritchie, during the development of the Unix operating system.

The important lesson is not simply “Dennis Ritchie created C.” The design problem C addressed was more interesting: programmers needed a language expressive enough for structured software development but powerful enough for operating-system and hardware-oriented work.

Higher-level programming ideas          Machine-oriented control
        │                                      │
        │   functions, loops, structures      │
        └─────────────── C ────────────────────┘
                         │
                 pointers, bits,
                 memory, addresses

That balance is why C is sometimes called a “middle-level language” in textbooks. This is an informal description, not an official classification in the C standard.

C is not only a historical language. It is still important because it exposes concepts that many higher-level languages hide behind abstractions.

#include <stdio.h>

int main(void)
{
    printf("Hello, CodeBhavya!\n");
    return 0;
}

#include <stdio.h>     → make I/O declarations available
        ↓
int main(void)         → define the starting function
        ↓
{                      → begin function body
        ↓
printf(...)           → perform output
        ↓
return 0;              → finish successfully
        ↓
}                      → end function body

These words are often mixed together by beginners. They are related, but they are not the same thing.

For learning purposes, it is useful to remember four major stages. A real toolchain may expose additional intermediate steps, but this model gives you the correct mental picture.

program.c
   │
   ├── Preprocessor ──→ expanded source
   │
   ├── Compiler ──────→ assembly/object representation
   │
   ├── Assembler ─────→ object file
   │
   └── Linker ────────→ executable
                              │
                              ↓
                     Operating system
                              │
                              ↓
                       Running process

When a program fails, first ask “At what stage did it fail?” This is much better than changing random lines.

Does it compile?
      │
      ├── No → inspect syntax/types/translation diagnostics
      │
      └── Yes
           ↓
      Does it link?
           │
           ├── No → inspect missing definitions/libraries
           │
           └── Yes
                ↓
          Does it run correctly?
                │
                ├── No → inspect runtime behavior
                │
                └── Yes, but wrong answer → inspect logic

The C standard defines the language and standard library. Compilers may also provide extra features that are not part of standard C.

Do not stare at an entire program and try to understand everything at once. Use a fixed reading order.

INPUT
  ↓
PROCESSING
  ↓
DECISION / LOOP
  ↓
OUTPUT
  ↓
CLEANUP (when resources require it)