Жоғары деңгейлі бағдарламалау тілдері

Programming language that abstracts details of computing hardware

In computer science, a high level programming language is a programming language with strong abstraction from the details of the computer. In contrast to low level programming languages, 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 "high level" a programming language is. In the 1960s, a high level programming language using a compiler was commonly called an autocode. Examples of autocodes are COBOL and Fortran. The first high level programming language designed for computers was Plankalkül, created by Konrad Zuse. However, it was not implemented in his time, and his original contributions were largely isolated from other developments due to World War II, aside from the language's influence on the "Superplan" language by Heinz Rutishauser and also to some degree ALGOL. The first significantly widespread high level language was Fortran, a machine independent development of IBM's earlier Autocode systems. The ALGOL family, with ALGOL 58 defined in 1958 and ALGOL 60 defined in 1960 by committees of European and American computer scientists, introduced recursion as well as nested functions under lexical scope. ALGOL 60 was also the first language with a clear distinction between value and name parameters and their corresponding semantics. ALGOL also introduced several structured programming concepts, such as the while do and if then else constructs and its syntax was the first to be described in formal notation – Backus–Naur form (BNF). During roughly the same period, COBOL introduced records (also called structs) and Lisp introduced a fully general lambda abstraction in a programming language for the first time.

"High level language" refers to the higher level of abstraction from machine language. Rather than dealing with registers, memory addresses, and call stacks, high level languages deal with variables, arrays, objects, complex arithmetic or Boolean expressions, subroutines and functions, loops, threads, locks, and other abstract computer science concepts, with a focus on usability over optimal program efficiency. Unlike low level assembly languages, high level languages have few, if any, language elements that translate directly into a machine's native opcodes. Other features, such as string handling routines, object oriented language features, and file input/output, may also be present. One thing to note about high level programming languages is that these languages allow the programmer to be detached and separated from the machine. That is, unlike low level languages like assembly or machine language, high level programming can amplify the programmer's instructions and trigger a lot of data movements in the background without their knowledge. The responsibility and power of executing instructions have been handed over to the machine from the programmer.

High level languages intend to provide features that standardize common tasks, permit rich debugging, and maintain architectural agnosticism; while low level languages often produce more efficient code through optimization for a specific system architecture. Abstraction penalty is the cost that high level programming techniques pay for being unable to optimize performance or use certain hardware because they don't take advantage of certain low level architectural resources. High level programming exhibits features like more generic data structures and operations, run time interpretation, and intermediate code files; which often result in execution of far more operations than necessary, higher memory consumption, and larger binary program size. For this reason, code which needs to run particularly quickly and efficiently may require the use of a lower level language, even if a higher level language would make the coding easier. In many cases, critical portions of a program mostly in a high level language can be hand coded in assembly language, leading to a much faster, more efficient, or simply reliably functioning optimised program. However, with the growing complexity of modern microprocessor architectures, well designed compilers for high level languages frequently produce code comparable in efficiency to what most low level programmers can produce by hand, and the higher abstraction may allow for more powerful techniques providing better overall results than their low level counterparts in particular settings. High level languages are designed independent of a specific computing system architecture. This facilitates executing a program written in such a language on any computing system with compatible support for the Interpreted or JIT program. High level languages can be improved as their designers develop improvements. In other cases, new high level languages evolve from one or more others with the goal of aggregating the most popular constructs with new or improved features. An example of this is Scala which maintains backward compatibility with Java, meaning that programs and libraries written in Java will continue to be usable even if a programming shop switches to Scala; this makes the transition easier and the lifespan of such high level coding indefinite. In contrast, low level programs rarely survive beyond the system architecture which they were written for without major revision. This is the engineering 'trade off' for the 'Abstraction Penalty'.

Examples of high level programming languages in active use today include Python, JavaScript, Visual Basic, Delphi, Perl, PHP, ECMAScript, Ruby, C#, Java and many others. The terms high level and low level are inherently relative. Some decades ago, the C language, and similar languages, were most often considered "high level", as it supported concepts such as expression evaluation, parameterised recursive functions, and data types and structures, while assembly language was considered "low level". Today, many programmers might refer to C as low level, as it lacks a large runtime system (no garbage collection, etc. ), basically supports only scalar operations, and provides direct memory addressing; it therefore, readily blends with assembly language and the machine level of CPUs and microcontrollers. Also, in the introduction chapter of The C Programming Language (second edition) by Brian Kernighan and Dennis Ritchie, C is described as "not a very high level" language. Assembly language may itself be regarded as a higher level (but often still one to one if used without macros) representation of machine code, as it supports concepts such as constants and (limited) expressions, sometimes even variables, procedures, and data structures. Machine code, in turn, is inherently at a slightly higher level than the microcode or micro operations used internally in many processors.

Alternatively, it is possible for a high level language to be directly implemented by a computer – the computer directly executes the HLL code. This is known as a high level language computer architecture – the computer architecture itself is designed to be targeted by a specific high level language. The Burroughs large systems were target machines for ALGOL 60, for example.