Imperative programming: Difference between revisions

Browse history interactively

← Previous edit

Content deleted Content added

VisualWikitext

Revision as of 02:39, 30 August 2024 edit Mike Schwartz (talk \| contribs) Extended confirmed users 3,808 edits →Rationale and foundations of imperative programming: Make a "partial improvement" ["P.I."] in the "non-" specific target for the wikilink that appears right after the words "... imperative languages, in addition, permit the", and right before [the next quoted phrase is only PART OF the rest of the sentence] the words "of complex expressions,". This "P.I." adds a "#fragment" suffix (namely, "#Computer_science") to point to a section [a partially specific part] of the destination article. ← Previous edit		Latest revision as of 12:55, 17 June 2025 edit undo 2a0d:6fc0:74b:a000:a13d:3d6c:51ec:a79b (talk) →Basic
(9 intermediate revisions by 6 users not shown)
Line 1: {{Short description\|Type of programming paradigm in computer science}} {{more citations needed\|date=October 2011}} In [[computer science]], '''imperative programming''' is a [[programming paradigm]] of [[software]] that uses [[Statement (computer science)\|statement]]s that change a program's [[state (computer science)\|state]]. In much the same way that the [[imperative mood]] in [[natural language]]s expresses commands, an imperative program consists of [[command (computing)\|command]]s for the [[computer]] to perform. Imperative programming focuses on describing ''how'' a program operates step by step (with general order of the steps being determined in [[source code]] by the placement of statements one below the other),<ref>{{Cite web \|last=Jain \|first=Anisha \|date=2022-12-10 \|title=Javascript Promises— Is There a Better Approach? \|url=https://medium.datadriveninvestor.com/javascript-promises-is-there-a-better-approach-dd6a0a329131 \|access-date=2022-12-20 \|website=Medium \|language=en \|archive-date=2022-12-20 \|archive-url=https://web.archive.org/web/20221220020247/https://medium.datadriveninvestor.com/javascript-promises-is-there-a-better-approach-dd6a0a329131 \|url-status=live }}</ref> rather than on high-level descriptions of its expected results. The term is often used in contrast to [[declarative programming]], which focuses on ''what'' the program should accomplish without specifying all the details of ''how'' the program should achieve the result.<ref>{{Cite web \|title=Imperative programming: Overview of the oldest programming paradigm \|url=https://www.ionos.com/digitalguide/websites/web-development/imperative-programming/ \|access-date=2022-05-03 \|website=IONOS Digitalguide \|date=21 May 2021 \|language=en \|archive-date=2022-05-03 \|archive-url=https://web.archive.org/web/20220503083342/https://www.ionos.com/digitalguide/websites/web-development/imperative-programming/ \|url-status=live }}</ref> ==Procedural programming== Line 90: Algol's direct descendants include [[Pascal (programming language)\|Pascal]], [[Modula-2]], [[Ada (programming language)\|Ada]], [[Delphi (software)\|Delphi]] and [[Oberon (programming language)\|Oberon]] on one branch. On another branch there's [[C (programming language)\|C]], [[C++]] and [[Java (programming language)\|Java]].<ref name="cpl_3rd-ch2-19"/> ===~~Basic~~BASIC=== [[BASIC]] (1964) stands for "Beginner's All Purpose Symbolic Instruction Code." It was developed at [[Dartmouth College]] for all of their students to learn.<ref name="cpl_3rd-ch2-30">{{cite book \| last = Wilson Line 139: * The ''global and static data'' region is located just above the ''program'' region. (The program region is technically called the ''text'' region. It's where machine instructions are stored.) :* The global and static data region is technically two regions.<ref name="geeksforgeeks">{{cite web \| url = https://www.geeksforgeeks.org/memory-layout-of-c-program/ \| title = Memory Layout of C Programs \| date = 12 September 2011 \| access-date = 25 May 2022 \| archive-date = 6 November 2021 \| archive-url = https://web.archive.org/web/20211106175644/https://www.geeksforgeeks.org/memory-layout-of-c-program/ \| url-status = live }}</ref> One region is called the ''initialized [[data segment]]'', where variables declared with default values are stored. The other region is called the ''[[.bss\|block started by segment]]'', where variables declared without default values are stored. :* Variables stored in the ''global and static data'' region have their [[Memory address\|addresses]] set at compile-time. They retain their values throughout the life of the process.