Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Nope. Pascal is still king here. The speed it compiles at is simply ridiculous. Largely this is because the way the modules are defined makes it a snap to pre-compile aggressively. You're simply not allowed to do things that would change the way a module is understood by the compiler based on context.

The biggest hold-up in the C world is rampant abuse of #include files.



Yea, change a certain .h file and you can go get a cup of coffee while waiting for the build to end. This can't ever happen with Java/C#.


Turbo Pascal is (was?) king here.

It's possible to make slow Pascal compilers. But Borland put a lot of effort into that, and it really set a very high standard.


> The biggest hold-up in the C world is rampant abuse of #include files.

true.

> Nope. Pascal is still king here.

for some values of "king" perhaps - perhaps it's faster to compile, but no arrays of varying lengths in a function call? and if i'm not mistake, a function must be defined before use..? pascal is incredibly restrictive, and perhaps that's why it's so fast.


It's very restrictive, but the compiler is unbelievably fast because of that.

I'm not going to argue that Pascal is somehow superior to C, it's far more limited, but there's lessons here to be learned on how to make a compiler rip through code.


Only if speaking of original Pascal, neither Extended Pascal nor Object Pascal suffer from those limitations.

When I learned C, after a few years of Pascal dialects C just felt like a stone age language.


> for some values of "king" perhaps - perhaps it's faster to compile, but no arrays of varying ...

Well, let's not change the goalpost - your initial assertion was that C has faster compile times. Then chances are that something's got to give, whether that is in the grammar, declaration order, etc.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: