<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.sarg.dev/index.php?action=history&amp;feed=atom&amp;title=High-level_programming_language</id>
	<title>High-level programming language - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.sarg.dev/index.php?action=history&amp;feed=atom&amp;title=High-level_programming_language"/>
	<link rel="alternate" type="text/html" href="https://wiki.sarg.dev/index.php?title=High-level_programming_language&amp;action=history"/>
	<updated>2026-06-23T14:40:40Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.44.2</generator>
	<entry>
		<id>https://wiki.sarg.dev/index.php?title=High-level_programming_language&amp;diff=134010&amp;oldid=prev</id>
		<title>imported&gt;Mindmatrix: revert to previous intro, though something that falls between these two would be preferred</title>
		<link rel="alternate" type="text/html" href="https://wiki.sarg.dev/index.php?title=High-level_programming_language&amp;diff=134010&amp;oldid=prev"/>
		<updated>2025-11-12T02:53:00Z</updated>

		<summary type="html">&lt;p&gt;revert to previous intro, though something that falls between these two would be preferred&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{Short description|Programming language that abstracts details of computing hardware}}&lt;br /&gt;
{{Use dmy dates|date=May 2023}}&lt;br /&gt;
{{Use American English|date=January 2019}}&lt;br /&gt;
&lt;br /&gt;
A &amp;#039;&amp;#039;&amp;#039;high-level programming language&amp;#039;&amp;#039;&amp;#039; is a [[programming language]] with strong [[Abstraction (computer science)|abstraction]] from the details of the [[computer]]. In contrast to [[low-level programming language]]s, it may use [[natural language]] elements, be easier to use, or may automate (or even hide entirely) significant areas of computing systems (e.g. [[memory management]]), making the process of developing a program simpler and more understandable than when using a lower-level language. The amount of abstraction provided defines how &amp;quot;high-level&amp;quot; a programming language is.&amp;lt;ref&amp;gt;{{cite web |archive-url=https://web.archive.org/web/20070826224349/http://www.ittc.ku.edu/hybridthreads/glossary/index.php |archive-date=2007-08-26 |url=http://www.ittc.ku.edu/hybridthreads/glossary/index.php |url-status=dead |title=HThreads - RD Glossary&amp;lt;!-- Bot generated title --&amp;gt;}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;High-level&amp;#039;&amp;#039; refers to a level of abstraction from the hardware details of a [[CPU |processor]] inherent in [[machine code |machine]] and [[assembly language| assembly]] code. Rather than dealing with registers, memory addresses, and call stacks, high-level languages deal with variables, arrays, [[object (computer science)|object]]s, arithmetic and [[Boolean expression]]s, [[function (computing)|functions]], loops, [[Thread (computer science)|thread]]s, locks, and other computer science abstractions, intended to facilitate [[Correctness (computer science)|correctness]] and [[software maintenance |maintainability]]. Unlike low-level [[assembly language]]s, high-level languages have few, if any, language elements that translate directly to a machine&amp;#039;s native [[opcode]]s. Other features, such as string handling, [[object-oriented programming]] features, and file input/output, may also be provided. A high-level language allows for source code that is detached and separated from the machine details. That is, unlike low-level languages like assembly and machine code, high-level language code may result in data movements without the programmer&amp;#039;s knowledge. Some control of what instructions to execute is handed to the compiler.&lt;br /&gt;
&lt;br /&gt;
==History==&lt;br /&gt;
{{Expand section|examples of more recent high-level programming languages|date=November 2025}}&lt;br /&gt;
In the 1960s, the term &amp;#039;&amp;#039;[[autocode]]&amp;#039;&amp;#039; was commonly used to describe a high-level programming language that relied on a compiler. Notable examples of such autocodes include COBOL and Fortran.&lt;br /&gt;
&lt;br /&gt;
The earliest high-level programming language ever designed for computers was [[Plankalkül]], developed by Konrad Zuse. However, it was never implemented during his lifetime, and his pioneering work remained largely disconnected from other advancements due to the disruptions of World War II. Even so, Plankalkül influenced Heinz Rutishauser’s [[Superplan]] language and, to a lesser extent, the development of ALGOL.&lt;br /&gt;
&lt;br /&gt;
The first high-level language to achieve widespread adoption was [[Fortran]], a machine-independent evolution of IBM’s earlier Autocode systems. Around the same time, the [[ALGOL]] family emerged—ALGOL 58 in 1958 and ALGOL 60 in 1960—created by joint committees of European and American computer scientists. ALGOL introduced key innovations such as recursion, nested functions under lexical scope, and a clear distinction between value and name parameters with their respective semantics. It also pioneered several structured programming concepts, including the &amp;#039;&amp;#039;while-do&amp;#039;&amp;#039; loop and &amp;#039;&amp;#039;if-then-else&amp;#039;&amp;#039; statements, and became the first language whose syntax was formally defined using [[Backus–Naur form]] (BNF).&lt;br /&gt;
&lt;br /&gt;
Meanwhile, [[COBOL]] brought the concept of [[Record (computer science)|records]] (also known as structs) into mainstream programming, and [[Lisp]] became the first language to implement a fully general [[Anonymous function|lambda abstraction]].&lt;br /&gt;
&lt;br /&gt;
==Abstraction penalty==&lt;br /&gt;
A high-level language provides features that standardize common tasks, permit rich debugging, and maintain architectural agnosticism. On the other hand, a low-level language requires the coder to work at a lower-level of abstraction which is generally more challenging, but does allow for [[program optimization |optimizations]] that are not possible with a high-level language. This &amp;#039;&amp;#039;abstraction penalty&amp;#039;&amp;#039; for using a high-level language instead of a low-level language is real, but in practice, low-level optimizations rarely improve performance at the [[user experience]] level.&amp;lt;ref&amp;gt;{{cite journal&lt;br /&gt;
 |author=Surana P &lt;br /&gt;
 |title=Meta-Compilation of Language Abstractions. &lt;br /&gt;
 |year=2006 &lt;br /&gt;
 |url=http://lispnyc.org/meeting-assets/2007-02-13_pinku/SuranaThesis.pdf&lt;br /&gt;
 |access-date=2008-03-17 &lt;br /&gt;
 |url-status=live&lt;br /&gt;
 |archive-url=https://web.archive.org/web/20150217154926/http://lispnyc.org/meeting-assets/2007-02-13_pinku/SuranaThesis.pdf &lt;br /&gt;
 |archive-date=2015-02-17 &lt;br /&gt;
}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{cite web&lt;br /&gt;
  | first = Argyn&lt;br /&gt;
  | last = Kuketayev&lt;br /&gt;
  | website = Application Development Trends&lt;br /&gt;
  | title = The Data Abstraction Penalty (DAP) Benchmark for Small Objects in Java.&lt;br /&gt;
  | url = http://www.adtmag.com/joop/article.aspx?id=4597&lt;br /&gt;
  | access-date = 2008-03-17&lt;br /&gt;
  | archive-url = https://web.archive.org/web/20090111091710/http://www.adtmag.com/joop/article.aspx?id=4597&lt;br /&gt;
  | archive-date = 2009-01-11&lt;br /&gt;
  | url-status = dead&lt;br /&gt;
  }}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite book&lt;br /&gt;
  | last1 = Chatzigeorgiou&lt;br /&gt;
  | last2 = Stephanides&lt;br /&gt;
  | editor-last = Blieberger&lt;br /&gt;
  | editor2-last = Strohmeier&lt;br /&gt;
  | contribution = Evaluating Performance and Power Of Object-Oriented Vs. Procedural Programming Languages&lt;br /&gt;
  | title = Proceedings - 7th International Conference on Reliable Software Technologies - Ada-Europe&amp;#039;2002&lt;br /&gt;
  | year = 2002&lt;br /&gt;
  | pages = 367&lt;br /&gt;
  | publisher = Springer&lt;br /&gt;
  }}&amp;lt;/ref&amp;gt; None the less, code that needs to run quickly and efficiently may require the use of a lower-level language, even if a higher-level language would make the coding easier to write and maintain. In many cases, critical portions of a program mostly in a high-level language are coded in assembly in order to meet tight timing or memory constraints. A well-designed compiler for a high-level language can produce code comparable in efficiency to what could be coded by hand in assembly, and the higher-level abstractions sometimes allow for optimizations that beat the performance of hand-coded assembly.&amp;lt;ref&amp;gt;&lt;br /&gt;
{{Cite journal&lt;br /&gt;
  |author1=Manuel Carro |author2=José F. Morales |author3=Henk L. Muller |author4=G. Puebla |author5=M. Hermenegildo | journal = Proceedings of the 2006 International Conference on Compilers, Architecture and Synthesis for Embedded Systems&lt;br /&gt;
  | title = High-level languages for small devices: a case study&lt;br /&gt;
  | url = http://www.clip.dia.fi.upm.es/papers/carro06:stream_interpreter_cases.pdf&lt;br /&gt;
  | year = 2006&lt;br /&gt;
  | publisher = ACM&lt;br /&gt;
  }}&amp;lt;/ref&amp;gt; Since a high-level language is designed independent of a specific computing [[Computer architecture |system architecture]], a program written in such a language can run on any computing context with a compatible compiler or interpreter. &lt;br /&gt;
&lt;br /&gt;
Unlike a low-level language that is inherently tied to processor hardware, a high-level language can be improved, and new high-level languages can evolve from others with the goal of aggregating the most popular constructs with improved features. For example, [[Scala (programming language)|Scala]] maintains backward compatibility with [[Java (programming language)|Java]]. Code written in Java continue to be usable even if a developer switches to Scala. This makes the transition easier and extends the lifespan of a [[codebase]]. In contrast, low-level programs rarely survive beyond the [[Computer architecture |system architecture]] which they were written for.&lt;br /&gt;
&lt;br /&gt;
== Relative meaning ==&lt;br /&gt;
{{refimprove section|date=October 2018}}&lt;br /&gt;
&lt;br /&gt;
The terms &amp;#039;&amp;#039;high-level&amp;#039;&amp;#039; and &amp;#039;&amp;#039;low-level&amp;#039;&amp;#039; are inherently relative, and languages can be compared as higher or lower level to each other. Sometimes the [[C (programming language)|C language]] is considered as either high-level or low-level depending on one&amp;#039;s perspective. Regardless, most agree that C is higher level than assembly and lower level than most other languages.&lt;br /&gt;
&lt;br /&gt;
C supports constructs such as expression evaluation, [[parameter |parameterized]] and recursive functions, data types and structures which are generally not supported in assembly or directly by a processor but C does provide lower-level features such as auto-increment and pointer math. But C lacks many higher-level abstracts common in other languages such as [[garbage collection]] and a built-in string type. In the introduction of [[The C Programming Language]] (second edition) by [[Brian Kernighan]] and [[Dennis Ritchie]], C is described as &amp;quot;not a very high level&amp;quot; language.&amp;lt;ref&amp;gt;{{cite book|last1=Kernighan|first1=Brian W.|last2=Ritchie|first2=Dennis M.|date=1988|title=The C Programming Language: 2nd Edition|url=https://books.google.com/books?id=FGkPBQAAQBAJ|url-status=bot: unknown|publisher=Prentice Hall|isbn=9780131103627|archive-url=https://web.archive.org/web/20221025180501/https://books.google.com/books?id=FGkPBQAAQBAJ|archive-date=25 October 2022|access-date=25 October 2022}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Assembly language is higher-level than machine code, but still highly tied to the processor hardware. However, assembly may provide some higher-level features such as [[Macro (computer science)|macro]]s, relatively limited expressions, constants, variables, procedures, and [[data structure]]s. &lt;br /&gt;
&lt;br /&gt;
[[Machine code]] is at a slightly higher level abstraction than the [[microcode]] or [[micro-operation]]s used internally in many processors.&amp;lt;ref&amp;gt;{{Cite book|title=The art of assembly language|last=Hyde, Randall.|date=2010|publisher=No Starch Press|isbn=9781593273019|edition= 2nd|location=San Francisco|oclc=635507601|url=https://books.google.com/books?id=sYHtTvQ-ObIC}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Execution modes ==&lt;br /&gt;
{{refimprove section|find=Execution modes|date=October 2018}}&lt;br /&gt;
The source code of a high-level language may be processed in various ways, such as:&lt;br /&gt;
&lt;br /&gt;
; Compiled: A [[compiler]] transforms source code into other code. In some cases, a compiler generates native machine code that is interpreted by the processor; however, many execution models today involve generating an [[intermediate representation]] (i.e. [[bytecode]]) that is later interpreted in software or converted to native code at runtime (via [[JIT compilation]]).&lt;br /&gt;
&lt;br /&gt;
; [[Transpiled]]: Code may be translated into source code of another language (typically lower-level) for which a compiler or interpreter is available. [[JavaScript]] and the [[C (programming language)|C]] are common targets for such translators. For example, C and C++ code can be seen as generated from Eiffel code when using the [[EiffelStudio]] IDE. In Eiffel, the &amp;#039;&amp;#039;translated&amp;#039;&amp;#039; process is referred to as &amp;#039;&amp;#039;transcompiling&amp;#039;&amp;#039; or &amp;#039;&amp;#039;transcompiled&amp;#039;&amp;#039;, and the Eiffel compiler as a transcompiler or [[source-to-source compiler]].&lt;br /&gt;
&lt;br /&gt;
; Software interpreted: A [[interpreter (software)|software interpreter]] performs the actions encoded in source code without generating native machine code.&lt;br /&gt;
&lt;br /&gt;
; Hardware interpreted: Although uncommon, a processor with a [[high-level language computer architecture]] can process a high-level language without a compilation step. For example, the [[Burroughs large systems]] were target machines for [[ALGOL 60]].&amp;lt;ref&amp;gt;{{Citation|last=Chu|first=Yaohan|chapter=Concepts of High-Level Language Computer Architecture|date=1975|pages=1–14|publisher=Elsevier|isbn=9780121741501|doi=10.1016/b978-0-12-174150-1.50007-0|title=High-Level Language Computer Architecture}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note that a language is not strictly interpreted or compiled. Rather, an execution model involves a compiler or an interpreter and the same language might be used with different execution models. For example, [[ALGOL 60]] and [[Fortran]] have both been interpreted even though they were more typically compiled. Similarly, Java shows the difficulty of trying to apply these labels to languages, rather than to implementations. Java is compiled to bytecode which is then executed by either interpreting in a [[Java virtual machine]] (JVM) or JIT compiled.&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
{{Portal|Computer programming}}&lt;br /&gt;
* [[Generational list of programming languages]]&lt;br /&gt;
* [[Categorical list of programming languages]]&lt;br /&gt;
* [[Very high-level programming language]]s&lt;br /&gt;
* [[Low-level programming language]]s&lt;br /&gt;
* [[High-level assembler]]&lt;br /&gt;
* [[Abstraction (computer science)]]&lt;br /&gt;
{{Clear}}&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
{{Reflist}}&lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
* http://c2.com/cgi/wiki?HighLevelLanguage - The [[WikiWikiWeb]]&amp;#039;s article on high-level programming languages&lt;br /&gt;
&lt;br /&gt;
{{Types of programming languages}}&lt;br /&gt;
{{Authority control}}&lt;br /&gt;
&lt;br /&gt;
{{DEFAULTSORT:High-Level Programming Language}}&lt;br /&gt;
[[Category:High-level programming languages| ]]&lt;br /&gt;
[[Category:Programming language classification]]&lt;/div&gt;</summary>
		<author><name>imported&gt;Mindmatrix</name></author>
	</entry>
</feed>