Programming paradigm

A programming paradigm is a style of structuring programs and expressing computation, shaped by characteristic concepts such as commands, functions, or logical relations.

Imperative programming: A programming style that expresses computation as commands changing a program’s state. It organizes computation as explicit steps and state changes.
State (computer science): The information retained by a computation that can affect its later behavior. Imperative styles make changes to state central to program execution.
Structured programming: A method of organizing control flow with sequence, selection, and iteration instead of arbitrary jumps. It disciplines imperative code without defining a wholly separate computational model.
C (programming language): A general-purpose programming language designed for efficient systems programming and low-level memory access. C is a prominent example of procedural and imperative programming.
Declarative programming: A programming style that describes desired results or relationships rather than prescribing every execution step. It contrasts with paradigms centered on explicit instructions.
Referential transparency: A property of expressions that can be replaced by their values without changing program behavior. Functional programming uses it to make expressions easier to reason about.
Unstructured programming: A programming style that relies on unrestricted jumps and tangled control flow. It contrasts with paradigms that impose clearer structures on program execution.
Haskell: A statically typed programming language with a strong emphasis on pure functional programming. Haskell makes functional programming principles explicit in a general-purpose language.
Functional programming: A programming style that emphasizes function evaluation, immutable data, and composition. It treats computation primarily as evaluating and composing functions.
Recursion: A method of defining or solving a problem in terms of smaller instances of itself. Functional programs often use recursive definitions instead of mutable loops.

Linked from 2 pages