Difference between revisions of "Imperative programming"
From Wiki @ Karl Jones dot com
Karl Jones (Talk | contribs) (First) |
Karl Jones (Talk | contribs) (Functional programming) |
||
| Line 4: | Line 4: | ||
The term is often used in contrast to [[declarative programming]], which focuses on what the program should accomplish without prescribing how to do it in terms of sequences of actions to be taken. | The term is often used in contrast to [[declarative programming]], which focuses on what the program should accomplish without prescribing how to do it in terms of sequences of actions to be taken. | ||
| + | |||
| + | == See also == | ||
| + | |||
| + | * [[Functional programming]] | ||
== External links == | == External links == | ||
* [https://en.wikipedia.org/wiki/Imperative_programming Imperative programming] @ Wikipedia | * [https://en.wikipedia.org/wiki/Imperative_programming Imperative programming] @ Wikipedia | ||
Revision as of 08:39, 5 June 2015
In computer science, imperative programming is a programming paradigm that describes computation in terms of statements that change a program state. In much the same way that the imperative mood in natural languages expresses commands to take action, imperative programs define sequences of commands for the computer to perform.
Imperative programming (necessary programming) is focused on describing how a program operates.
The term is often used in contrast to declarative programming, which focuses on what the program should accomplish without prescribing how to do it in terms of sequences of actions to be taken.
See also
External links
- Imperative programming @ Wikipedia
