Timeline for Why are standard libraries not programming language primitives?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 30, 2019 at 1:01 | comment | added | alephzero | @JaredSmith I would say it is now the general case, not special at all. Nobody writes "a compiler" as a monolithic application any more. They produce compiler systems instead. Most of the functionality of complete compiler is completely independent of the particular language that is being compiled, and much of the language-dependent part can be done by supplying different data defining the grammar of the language, not by writing different code for each language you want to compile. | |
| Jan 30, 2019 at 0:45 | comment | added | Jared Smith | @gnasher729 isn't that a bit of a special case (along with other multilanguage targets like the CLR)? | |
| Jan 29, 2019 at 23:20 | comment | added | gnasher729 | "any self-respecting compiler should be self-hosted" - not at all. It would be pointless to have versions of say LLVM written in C, C++, Objective-C, Swift, Fortran and so on to compile all these languages. | |
| Jan 29, 2019 at 22:32 | history | answered | Jared Smith | CC BY-SA 4.0 |