Timeline for How does a compiler work when it's not directly compiling to machine code
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 17, 2019 at 12:34 | comment | added | Jörg W Mittag | BTW, the main reason to use a compiler → bytecode VM multi-stage approach is not so much caching and reusing the bytecode. In fact, CPython is pretty unique in that aspect, most similar implementations don't do that. The main reason is that you convert a language that is easy to write and read but hard to interpret into a language that is easy to interpret without caring about readability and writability. | |
| Feb 17, 2019 at 10:35 | history | edited | JacquesB | CC BY-SA 4.0 |
added 291 characters in body
|
| Feb 17, 2019 at 10:17 | history | edited | JacquesB | CC BY-SA 4.0 |
added 738 characters in body
|
| Feb 17, 2019 at 10:07 | history | answered | JacquesB | CC BY-SA 4.0 |