News for hackers. Stuff that matters.
Re:Apple's Module proposal to replace headers for C-based la... by rossjudson on Monday November 26, 2012 @04:56PM (#4834259)
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.

Re:Apple's Module proposal to replace headers for C-based la... by coliveira on Monday November 26, 2012 @09:49PM (#4835360)
Part 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.
Re:Apple's Module proposal to replace headers for C-based la... by pjmlp on Tuesday November 27, 2012 @04:22AM (#4836362)
The 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.

Re:Apple's Module proposal to replace headers for C-based la... by rikthevik on Tuesday November 27, 2012 @12:53AM (#4835859)
If I remember correctly, it's a single pass parser, which is why you generally write get to your code upside down.
Re:Apple's Module proposal to replace headers for C-based la... by masklinn on Tuesday November 27, 2012 @04:49AM (#4836422)
Also due to the java compiler doing very little work (it's a really dumb compiler)
Re:Apple's Module proposal to replace headers for C-based la... by pkolaczk on Tuesday November 27, 2012 @08:11AM (#4836954)
It 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).