Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Von Neumann programming languages
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{Multiple issues| {{one source|date=August 2010}} {{original research|date=August 2010}} }} A '''von Neumann language''' in [[computing]] is a [[programming language]] that is a high-level abstract [[isomorphism|isomorphic]] copy of a [[von Neumann architecture]].<ref>{{cite journal |last1=Backus |first1=John |title=Can programming be liberated from the von Neumann style? a functional style and its algebra of programs |url=https://dl.acm.org/doi/10.1145/359576.359579 |journal=Communications of the ACM |publisher=Association for Computing Machinery |access-date=15 July 2023 |pages=613β641 |doi=10.1145/359576.359579 |date=1 August 1978|volume=21 |issue=8 }}</ref> {{As of|2009}}, most current programming languages fit into this description{{Citation needed|date=August 2010}}, likely as a consequence of the extensive domination of the von Neumann computer architecture during the past 50 years. The differences between [[Fortran]], [[C (programming language)|C]], and even [[Java (programming language)|Java]], although considerable, are ultimately constrained by all three being based on the programming style of the von Neumann computer.{{Citation needed|date=August 2010}} If, for example, Java objects were all executed in parallel with asynchronous [[message passing]] and attribute-based declarative addressing, then Java would not be in the group. The isomorphism between von Neumann programming languages and architectures is in the following manner: * program variables β computer storage cells * control statements β computer test-and-jump instructions * assignment statements β fetching, storing instructions * expressions β memory reference and arithmetic instructions. ==Criticism== [[John Backus]] asserted that assignment statements in von Neumann languages split programming into two worlds. The first world consists of ''expressions'', an orderly [[mathematical space]] with potentially useful algebraic properties: most computation takes place here. The second world consists of ''statements'', a disorderly mathematical space with few useful mathematical properties ([[structured programming]] can be seen as a limited [[heuristic]] that does apply in this space, though). Backus claimed that by 1978 there existed in [[computer science]] a [[vicious cycle]] where the long-standing emphasis on von Neumann languages has continued the primacy of the von Neumann computer architecture, and dependency on it has made non-von Neumann languages uneconomical and thus limited their further development: the lack of widely available and effective non-von Neumann languages has deprived computer designers of the motivation and the intellectual foundation needed to develop new computer architectures.<ref>[https://web.archive.org/web/20070328213749/http://www-03.ibm.com/ibm/history/exhibits/builders/builders_backus3.html IBM Archives: John Backus]</ref> ==Presence in modern systems== Many modern processors now contain multiple processing cores, and multi-threaded programming is usually the most efficient way to use more computational power in a single program. Some modern processors are highly optimized with techniques including [[out-of-order execution]], but with complex logic to detect when this can be done without violating the von Neumann semantics of the logical programming model. Separate instruction and data caches are widely used, making the hardware a [[Modified Harvard architecture]], but again with logic to detect cases where the optimization fails, to be able to execute [[Self-modifying code#Interaction of cache and self-modifying code|self-modifying code]]. Some specialized processors (including [[GPU]]s) are very wide [[multiple instruction, multiple data]] (MIMD) devices. General-purpose CPUs do commonly have multiple cores, but each one is fast enough that many programs are fast enough without parallelizing single tasks. (Threads are commonly used to deal with asynchronous inputs or outputs, especially in a [[GUI]].) General-purpose CPUs are technically MIMD devices, but usually only hardware designed from the ground up for MIMD programming is referred to as MIMD. Many widely used programming languages such as [[C (programming language)|C]], [[C++]] and [[Java (programming language)|Java]] have ceased to be strictly von Neumann by adding support for parallel processing, in the form of [[Thread (computing)|threads]]. However, most of the categorically ''non''-von Neumann languages are also [[Functional programming|functional]] languages and have not achieved widespread use. == See also == * [[Homoiconicity]] ==References== <references/> {{DEFAULTSORT:Von Neumann Programming Languages}} [[Category:Programming language classification]] [[Category:John von Neumann]]
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)
Pages transcluded onto the current version of this page
(
help
)
:
Template:As of
(
edit
)
Template:Citation needed
(
edit
)
Template:Cite journal
(
edit
)
Template:Multiple issues
(
edit
)