Source code

Source Code is a 2011 science fiction action thriller film directed by Duncan Jones and written by Ben Ripley.

Uses your system voice; voice and rate in settings.

≈ 7 min read

Cite, export and learn8 citation formats · 8 exports · lesson and quiz

Names in other languages

No names in other languages are held for this entry yet.

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

Source Code is a 2011 science fiction action thriller film directed by Duncan Jones and written by Ben Ripley. It stars Jake Gyllenhaal as a US Army officer who is sent into an eight-minute virtual re-creation of a real-life train explosion, and tasked with determining the identity of the terrorist who bombed it. Michelle Monaghan, Vera Farmiga, and Jeffrey Wright play supporting roles.

It had its world premiere on March 11, 2011, at South by Southwest and was released by Summit Entertainment on April 1, 2011, in North America and Europe. It received positive reviews from critics and was a box office success, grossing $147 million on a $32 million budget.

source code for a "Hello world" program. Taken from the seminal book The C Programming Language, it originates from Brian Kernighan in the Bell Laboratories in 1974. In computing, source code, or simply code or source, is human readable plain text that can eventually result in controlling the behavior of a computer .

In order to control a computer, it must be processed by a computer program either executed directly via an interpreter or translated into a more computer-consumable form such as via a compiler. Sometimes, code is compiled directly to machine code so that it can be run in the native language of the computer without further processing.

Many modern environments, though, involve compiling to an intermediate representation such as bytecode that can either run via an interpreter or be compiled on-demand to machine code via just-in-time compilation. Source code is typically stored in source files.

Beyond software, the term source file is used across other domains — such as documents, images, hardware design, and typography — to refer to the original, editable file from which a distribution format is derived.

Background

The first programmable computers, which appeared at the end of the 1940s, were programmed in machine code (simple instructions that could be directly executed by the processor). Machine language was difficult to debug and was not portable between different computer systems. Initially, hardware resources were scarce and expensive, while human resources were cheaper.

As programs grew more complex, programmer productivity became a bottleneck. This led to the introduction of high-level programming languages such as Fortran in the mid-1950s. These languages abstracted away the details of the hardware, and were designed to express algorithms that could be understood more easily by humans.

As instructions distinct from the underlying computer hardware, software is therefore relatively recent, dating to these early high-level programming languages such as Fortran, Lisp, and Cobol. The invention of high-level programming languages was simultaneous with the compilers needed to translate the source code automatically into machine code that can be directly executed on the computer hardware.

Some definitions of source code consider it to be the form of code that is modified directly by humans, typically in a high-level programming language. Object code can be directly executed by the machine and is generated automatically from the source code, often via an intermediate step, assembly language.

While object code will only work on a specific platform, source code can be ported to a different machine and recompiled there. For the same source code, object code can vary significantly—not only based on the machine for which it is compiled, but also based on performance optimization from the compiler.

Estimation

The number of source lines of code (SLOC) is often used as a metric when evaluating the productivity of computer programmers, the economic value of a code base, effort estimation for projects in development, and the ongoing cost of software maintenance after release.

Communication

Source code is also used to communicate algorithms between parties, e.g., code snippets online or in books. Computer programmers can find it helpful to review extant source code to learn about programming techniques. The sharing of source code between developers is often cited as a contributing factor to the maturing of their programming skills.

Some consider source code an expressive artistic medium. Source code often contains comments—blocks of text marked for the compiler to ignore. This content is not part of the program logic, but is instead intended to help readers understand the program.

Companies often keep the source code confidential in order to hide algorithms considered a trade secret. Proprietary, secret source code and algorithms are widely used for sensitive government applications such as criminal justice, which results in black box behavior with a lack of transparency into the algorithm's methodology.

The result is avoidance of public scrutiny of issues such as bias.

Modification

Access to the source code (not just the object code) is essential to modifying it. Understanding extant code is necessary to understand how it works and before modifying it. The rate of understanding depends both on the code base as well as the skill of the programmer.

Experienced programmers have an easier time understanding what the code does at a high level. Software visualization is sometimes used to speed up this process. Many software programmers use an integrated development environment (IDE) to improve their productivity.

IDEs typically have several features built in, including a source-code editor that can alert the programmer to common errors. Modification often includes code refactoring (improving structure without changing function) and restructuring (improving structure and function simultaneously).

Nearly every change to code introduces new bugs or unexpected ripple effects, which require another round of fixes. Code reviews by other developers are often used to scrutinize new code added to a project. The purpose of this phase is often to verify that the code meets style and maintainability standards and that it is a correct implementation of the software design.

According to some estimates, code review dramatically reduce the number of bugs persisting after software testing is complete. Along with software testing that works by executing the code, static program analysis uses automated tools to detect problems with the source code. Many IDEs support code analysis tools, which might provide metrics on the clarity and maintainability of the code.

Debuggers are tools that often enable programmers to step through execution while keeping track of which source code corresponds to each change of state.

Compilation and execution

Source code files in a high-level programming language must go through a stage of preprocessing into machine code before the instructions can be carried out. After being compiled, the program can be saved as an object file and the loader (part of the operating system) can take this saved file and execute it as a process on the computer hardware.

Some programming languages use an interpreter instead of a compiler. An interpreter converts the program into machine code at run time, which makes them 10 to 100 times slower than compiled programming languages.

Quality

Software quality is an overarching term that can refer to a code's correct and efficient behavior, its reusability and portability, or the ease of modification. It is usually more cost-effective to build quality into a product from the start rather than try to add it later in a development process.

Higher quality code reduces lifetime cost to both suppliers and customers as via higher reliability and maintainability. Maintainability is the quality of software enabling it to be easily modified without breaking extant functions. Following coding conventions such as using clear function and variable names that correspond to their purpose makes maintenance easier.

Use of conditional loop statements only if the code could execute more than once, and eliminating code that will never execute can also increase understandability. Many software development organizations neglect maintainability during the development phase, even though it will increase long-term costs.

Technical debt is incurred when programmers, often out of laziness or urgency to meet a deadline, choose quick and dirty solutions rather than build maintainability into their code. A common cause is underestimates in software development effort estimation, leading to insufficient resources allocated to development.

A challenge with maintainability is that many software engineering courses do not emphasize it. Development engineers who know that they will not be responsible for maintaining the software do not have an incentive to build in maintainability.

Text derived from https://en.wikipedia.org/w/index.php?oldid=1378413452 under CC BY-SA 4.0; modifications have been made.

Words in each sectionModificationModificationModification: 266 words266BackgroundBackgroundBackground: 258 words258QualityQualityQuality: 249 words249CommunicationCommunicationCommunication: 158 words158Compilation and executi…Compilation and executionCompilation and execution: 93 words93EstimationEstimationEstimation: 43 words43
Words in each section. Measured from the stored article body; sections below the minimum are not plotted.

Provenance

snapshot enwiki-001372056005 · captured 2026-10-04 · ledger · version history

Cite this page as: encyclopegia.org, “Source code”, snapshot enwiki-001372056005. https://encyclopegia.org/a/source-code

Sources cited in this revision

23 named source(s) extracted from the cited revision. A source with no author is shown by its publication; nothing is invented.