Simply writing source code is not sufficient
: you need to turn the source code into something executable. Programming languages implement two ways: compilers and interpreters. While interpreters convert the line of code that is currently running, compilers convert the source code all at once, which takes a lot of time - time for you to goof off. After compiling the resulting code will run faster than interpreted code, since it's already all been translated. |+|
Simply writing source code is not sufficientyou to into executable. . of , the code, a for the .
| || |
|−|The title text refers to a time where code compiling is not a legitimate response. |+|
title text to .
| || |
Revision as of 21:19, 8 August 2013
|| This explanation may be incomplete or incorrect: |
Please include the reason why this explanation is incomplete, like this:
If you can address this issue, please edit the page! Thanks.
Simply writing the source code is not sufficient, you have to compile this, turning it into executable files. At large projects this will take a long time, depending on the power of the computer it could be more than one hour. As of 2013, the Linux Kernel contains over 15 Million lines of code, a hard job for the compiler.
In general, programming languages are implemented in two ways: Interpreters and Compilers. Interpreters convert the code at the time when it's currently running (PHP is only one example), but compilers convert the source code all at once into executable files. After compiling the resulting code will run much faster than interpreted code, since it's already all been translated into the proper binary language.
In the title text Cueball admits that he did steal LCD displays, but only because he had to wait for the compiler.
add a comment! ⋅ add a topic (use sparingly)! ⋅ refresh comments!
- The #1 Programmer Excuse for Legitimately Slacking Off: “My code's compiling.”
- [Two programmers are sword-fighting on office chairs in a hallway. An unseen manager calls them back to work through an open office door.]
- Manager: Hey! Get back to work!
- Programmer: Compiling!
- Manager: Oh. Carry on.
I was sooo amused when I heard about the most common error report when Delphi was released to the linux platform: "the compile button doesn't do anything"...
The "fix" was to introduce a checkbox that defaulted to not close the compile window once complete :-)
For being so open-sourced they are quite close-minded ;-)
Usually interpreters don't create any code but use the source language as instructions to the interpreter. The situation is complicated by the existence of compilers which compile to an intermediate code (Java byte code for example), then compile the byte code to machine code.
Jstout (talk) 21:54, 13 December 2013 (UTC)
220.127.116.11 07:04, 10 November 2013 (UTC)Nicklas
- (In response to the JavaByte thing, whoever said that) I just revamped the explanation (because it looked like two different explanations mashed together). Now it's not repetitious, but longer than I had intended it to be. It would have been even longer had I gone into Java, so I left that out. However, I would say that Java (human writable) source code is 'compiled' into Javabyte code, which is then 'interpretted' by the Java Engine on the end-user's machine. But the original compilation puts it in an easier-to-interpret form than any human-written version would be, even whilst being still flexible across differing platforms. However, it can be a fuzzy line, these days, what exactly does what. YMMV. 18.104.22.168 00:30, 8 September 2015 (UTC)
"Liquid Crystal Display Displays" This bothers me. 22.214.171.124 19:59, 13 March 2014 (UTC)
- https://en.wikipedia.org/wiki/RAS_syndrome -- Wesha (talk) 19:36, 11 May 2015 (UTC)
Made it into a wiki link and removed Displays. Kynde (talk) 20:10, 28 March 2014 (UTC)