6 ms·
I only encountered Plan 9 once, and then only the header inclusion scheme it promotes for it's C code. Which IIRC goes like 'header files must not include other
by stinos 12y ago
I only encountered Plan 9 once, and then only the header inclusion scheme it promotes for it's C code. Which IIRC goes like 'header files must not include other header files hence every source file has to include the headers for all declarations used in that source file and in the headers it includes'. Which means when for any header file you want to include in your source you have to go figure out which headers are needed to pull in all declarations. For every single soure file. I really failed to see how any possible benefits of that would outweigh the cons.
- blablabla123 12y agoI think the Plan 9 hackers really try to avoid the C preprocessor ;)
- andrewchambers 12y agoI wouldn't be surprised if plan9 builds are an order of magnitude faster per LoC - Deeply nested includes and cyclic includes waste a huge amount of time. Avoiding cyclic dependencies might also be a good thing in terms of overall software design.
- dorfsmay 12y agoCompile time, sure, but that shouldn't influence running time.
- f2f 12y agoplan9 kernel builds take less that 10 seconds.
- andrewchambers 12y agoYeah, this is awesome... If gcc or the linux kernel compiled in 10 seconds, the world would be a better place.