4 ms·
Yeah. Compile times there were ridiculously fast, bordering on interactive. Go follows the same path. Java has very fast compilation as well, due in no small p
by rossjudson 14y ago
Yeah. Compile times there were ridiculously fast, bordering on interactive. Go follows the same path.
Java has very fast compilation as well, due in no small part to tossing the preprocessor and having fast binary imports.
- coliveira 14y agoPart of the advantage of Pascal at the time is that it was created explicitly to allow for fast parsing. C and especially C++ are much harder to parse.
- rikthevik 14y agoIf I remember correctly, it's a single pass parser, which is why you generally write get to your code upside down.
- pjmlp 14y agoThe main advantage was still the possibility of having binary modules, without parsing the same imports multiple times during "make world" compilation. Just as input, the ISO Pascal eventually got the changes that were available in Turbo Pascal and Mac Pascal (known as ISO Extended Pascal), but by then most people considered Turbo Pascal the _de facto_ standard.
- masklinn 14y agoAlso due to the java compiler doing very little work (it's a really dumb compiler)
- pkolaczk 14y agoIt does all the same work as a C++ compiler, except optimization phase. Yet any C++ compiler with optimization turned off is still order of magnitude slower. The key differences are: - Java has a much simpler grammar to parse. - Everything is compiled at most once. - Encapsulation is stronger: private class members are not exposed in public class ABI and external code doesn't depend on them (this also extremely improves recompilation times - no need to compile half of the project because you changed a private method).