Timeline for How do I create my own programming language and a compiler for it
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2011 at 21:41 | comment | added | Donal Fellows | No vote up from me: while compilers have two basic parts, one of them is to build an abstract description of the program (that's typically broken down into scanning and parsing) and the other to write a version of that abstract description out again in some other form (e.g., machine code). (Side note: Optimizing compilers typically try to improve the abstract description before writing it out, but that's a refinement.) | |
| Jun 16, 2011 at 13:31 | history | made wiki | Post Made Community Wiki by Michael Ekstrand | ||
| Jun 16, 2011 at 7:31 | comment | added | Macke | Uhm. The compiler, after scanning/parsing needs to do type-checking/inference, optimization, register allocation, etc, etc. These steps be anything but simple. (When using interpreted code, you just defer these parts to the runtime stage.) | |
| Jun 15, 2011 at 20:44 | comment | added | Neil Butterworth | Conceptually simple? Yes. Actually simple? No. | |
| Jun 15, 2011 at 20:39 | history | answered | Jerr | CC BY-SA 3.0 |