Source code: Difference between revisions
FosterHaven (talk | contribs) rewrite |
Ilyagredasov (talk | contribs) No edit summary Tags: Mobile edit Mobile web edit |
||
| (10 intermediate revisions by 9 users not shown) | |||
| Line 1: | Line 1: | ||
'''Source code''' is a collection of text files containing instructions that a computer either runs as-is (interpretation) or translates into an executable file beforehand (compilation / assembly). Source code is written using a human-readable computer language so that it can be translated by a compiler or an interpreter. It's also possible to decompile an executable file, though decompilers aren't as common. | '''Source code''' is a collection of text files containing instructions that a computer either runs as-is (interpretation) or translates into an executable file beforehand (compilation/assembly). Source code is written using a human-readable computer language so that it can be translated by a compiler or an interpreter. It's also possible to decompile an executable file, though decompilers aren't as common. | ||
The language used changes how the source code is read, and just like emulation it too has its own high and low-level types. If a program were written in an assembly language (which often involves taking advantage of system-specific attributes), an assembler would write the machine code "word for word," reflecting how the machine takes instructions. If a program were written in a low-level language, a compiler would read the code and translate the equivalent in machine code. If a program were written in a high-level language, it would often work without requiring a compiler. Some compilers and interpreters also do error checking to make sure the programmer's code is either properly written or formatted. Many languages also check that the code won't inherently cause bugs, such as Rust. | The language used changes how the source code is read, and just like emulation it too has its own high and low-level types. If a program were written in an assembly language (which often involves taking advantage of system-specific attributes), an assembler would write the machine code "word for word," reflecting how the machine takes instructions. If a program were written in a low-level language, a compiler would read the code and translate the equivalent in machine code. If a program were written in a high-level language, it would often work without requiring a compiler. Some compilers and interpreters also do error checking to make sure the programmer's code is either properly written or formatted. Many languages also check that the code won't inherently cause bugs, such as Rust. | ||
| Line 6: | Line 6: | ||
==Language levels== | ==Language levels== | ||
Software can be programmed in many different languages (even multiple in one program), and just like [[High/Low level emulation|high and low level emulation]], they have different levels of abstraction. Here are the different ones, from lowest to highest. | Software can be programmed in many different languages (even multiple in one program), and just like [[High/Low level emulation|high and low-level emulation]], they have different levels of abstraction. Here are the different ones, from lowest to highest. | ||
===Assembly=== | ===Assembly=== | ||
| Line 20: | Line 20: | ||
===High=== | ===High=== | ||
High-level languages push away most system specific quirks in favor of instructions intended to work on any platform. This was pioneered by Java, whose goal was for developers to "write once, run anywhere". | High-level languages push away most system-specific quirks in favor of instructions intended to work on any platform. This was pioneered by Java, whose goal was for developers to "write once, run anywhere". | ||
In high-level languages, many of the same instructions can be run across different architectures and platforms. They may have a compiler, a compiler cache, a [[dynamic recompilation|dynamic recompiler]], and/or an interpreter. | In high-level languages, many of the same instructions can be run across different architectures and platforms. They may have a compiler, a compiler cache, a [[dynamic recompilation|dynamic recompiler]], and/or an interpreter. | ||
| Line 27: | Line 27: | ||
[[wikipedia:Esoteric programming language|Esoteric languages]] are built around a specific idea or a joke, as part of a challenge. These languages are intended to be comedic, confusing, and/or thought-provoking. | [[wikipedia:Esoteric programming language|Esoteric languages]] are built around a specific idea or a joke, as part of a challenge. These languages are intended to be comedic, confusing, and/or thought-provoking. | ||
One example includes [[wikipedia:Brainfuck|Brainfuck]], a <abbr title="Meaning it can solve any problem a Turing machine can.">Turing-complete</abbr> programming language with only eight one-character commands (as opposed to the thousands of standard languages and architectures) and one instruction pointer. Another is [[wikipedia:Shakespeare Programming Language|Shakespeare]], a programming language designed to resemble a Shakespearean play. There's also [https://github.com/ | One example includes [[wikipedia:Brainfuck|Brainfuck]], a <abbr title="Meaning it can solve any problem a Turing machine can.">Turing-complete</abbr> programming language with only eight one-character commands (as opposed to the thousands of standard languages and architectures) and one instruction pointer. Another is [[wikipedia:Shakespeare Programming Language|Shakespeare]], a programming language designed to resemble a Shakespearean play. There's also [https://github.com/RockstarLang/rockstar Rockstar], a language designed around "the lyrical conventions of 1980s hard rock and power ballads", meant to lampoon the software industry's use of "rockstar developers" in recruiting. | ||
==Version control== | ==Version control== | ||
| Line 33: | Line 33: | ||
==Licensing== | ==Licensing== | ||
{{Main|Licensing}} | |||
Software is copyrightable, but the source code can be made available to users however the author chooses. A copyright license is a legal document that tells people how the software can be used and what limitations come with using it. | Software is copyrightable, but the source code can be made available to users however the author chooses. A copyright license is a legal document that tells people how the software can be used and what limitations come with using it. | ||
The more successful emulation projects are often open-source (though you definitely will find exceptions). | |||
The more successful emulation projects are often open source (though you definitely will find exceptions). | |||
==See also== | ==See also== | ||
* [[Dynamic recompilation]] | * [[Dynamic recompilation]] | ||
* [[ROM | * [[ROM hacking resources]] | ||
<!-- | <!-- | ||
==References== | ==References== | ||