What C Is and How C Programs Run

C is a compiled language: you write a source file, a toolchain turns it into a program for a specific environment, and that program runs outside the browser. Before adding more syntax, learn the complete path that makes a tiny C program real.

Map the system before learning the details

What C is—and what it is not

C is a general-purpose programming language with a small core and a close relationship to the memory and operating-system services beneath many programs. Operating systems, embedded devices, databases, tools, and performance-sensitive libraries often use it because C gives programmers direct control over data representation and program boundaries.

C source is not executed directly by a web browser. A C implementation—commonly a compiler plus a linker—translates source into an executable for a target environment. That distinction matters: a source file can be portable in intent, while the executable is built for a particular operating system and processor combination.

Follow one program through its lifecycle

For a first program, think in four visible hand-offs. Toolchains combine or optimize some of these steps, but the responsibilities stay useful to name.

1. 01
   Write source

   You save readable instructions in a file such as hello.c.

2. 02
   Preprocess and compile

   Directives such as #include are handled, then C source is translated into object code while the compiler reports syntax and type problems it can detect.

3. 03
   Link

   The linker combines your object code with required library code, including the implementation behind standard-library calls such as printf.

4. 04
   Load and run

   Your operating system starts the executable, the C runtime reaches main, and your statements create observable output or effects.

Errors point to different stages. A missing semicolon is usually a compiler diagnostic. A missing function implementation may be a linker error. A program that starts but behaves wrongly is a runtime or logic problem. Read the stage first; it tells you where to investigate.

Run a first C program

The program below includes the declarations for standard input/output, defines the conventional entry function, asks printf to display a line, and returns a success status. Predict the terminal text before you run it. Then replace the greeting and run it again.

#include <stdio.h>

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

Edit the program, predict its output, then run it.

Read the program line by line

Use output deliberately

printf is useful because its format string can combine ordinary text with values. The placeholder %d requests an integer, and the following argument supplies that integer. The format and the supplied values must agree—later lessons will cover types in depth, so treat that pairing as an important contract from the beginning.

#include <stdio.h>

int main(void) {
  int sessions = 4;
  int completed = 1;
  int remaining = sessions - completed;

  printf("Remaining sessions: %d\n", remaining);
  return 0;
}

Edit the program, predict its output, then run it.

Compile the same source locally

The browser runner is intentionally limited to the concepts in this lesson. A local compiler is the authority for real C code because it knows your system, target, libraries, and full language features. Save the first example as hello.c, then use the command appropriate to your environment.

The warning flags are deliberately strict: -Wall and -Wextra ask for common warning groups, while -Wpedantic asks for warnings about non-standard extensions. They help you form the habit of fixing evidence early.

Repair one compiler error

This program has one missing semicolon after the printf call. The runner reports the same category of mistake a compiler will: it cannot determine where that statement ends. Add only the semicolon, run again, and notice how a one-character repair restores the whole program.

#include <stdio.h>

int main(void) {
  printf("The compiler needs punctuation.\n")
  return 0;
}

Edit the program, predict its output, then run it.

Independent lab: make a terminal welcome

Now work without copying a prior output. Change the learner name, write a second sentence with puts, then add one more printf line. Keep the header, main signature, braces, and return 0; intact. Run the result and explain which line creates each terminal line.

#include <stdio.h>

int main(void) {
  const char *learner = "Ada";

  printf("Welcome, %s!\n", learner);
  puts("C turns source into a program.");
  return 0;
}

Edit the program, predict its output, then run it.

Lesson review

You now have the key orientation for the rest of C: source is not the executable, headers provide declarations, the compiler and linker have different jobs, the runtime reaches main, and terminal output comes from deliberate function calls. Use the checklist to decide whether the next lesson will build on a real understanding.

• I can name the source, compiler, linker, executable, and runtime stages in order.
• I can explain why #include <stdio.h> appears before a program that uses printf.
• I can identify the entry point, a statement boundary, a newline escape, and an exit status.
• I can run a warning-enabled local build and use a diagnostic to make one small repair.