One advantage to not including any OS headers or standard C/C++ headers is that I get to enjoy blazing fast build times on my old-ish quad core.

Source

URL: https://x.com/EricLengyel/status/931338437902372867
Author: Eric Lengyel (@EricLengyel)
Posted: 2017-11-17 01:49:21

Thread

1/ @EricLengyel

One advantage to not including any OS headers or standard C/C++ headers is that I get to enjoy blazing fast build times on my old-ish quad core. Compiling the entire Tombstone Engine from scratch only takes 51 s. The game I’m working on can be fully recompiled in 34 s.

Branches: 2017-11-17-Doomed_Daniel-i-think-often-its-good-enough-to-not-include, 2017-11-17-esmolikowski-a-lot-of-that-comes-down-to-proper-usage-of-c, 2017-11-17-lectem-just-curious-what-is-the-build-system-involved, 2017-11-17-igorst-on-the-other-hand-it-is-sad-what-is-considered

type	archive
source	twitter
date	2017-11-17
tags	archive, twitter, ericlengyel
description	One advantage to not including any OS headers or standard C/C++ headers is that I get to enjoy blazing fast build times on my old-ish quad core.

Threadwell

Explorer

Recent Notes

DemetriSpanos

NOTimothyLottes

bonzajplc

One advantage to not including any OS headers or standard C/C++ headers is that I get to enjoy blazing fast build times on my old-ish quad core.

Source

Thread

@EricLengyel I think often it's good enough to not include system headers in your own headers, but only .cpp where needed (and maybe own headers that are only used in a few .cpp's)

@EricLengyel A lot of that comes down to proper usage of C++.

@EricLengyel on the other hand it is sad what is considered blazing fast in C++ compiler world.

@EricLengyel Just curious, what is the build system involved?