Earlier quoted context omitted.
Some C++ related 'best practices' off the top of my head: - put each class into its own header/source file pair (a great way to explode your build times!) - generally replace all raw pointers with shared_ptr or unique_ptr - general software patterns like model-view-controller, a great way to turn a handful lines of code into dozens of files with hundreds of lines each - use exceptions for error handling (although the…
> put each class into its own header/source file pair (a great way to explode your build times!) Is that really sufficient to explode build times on its own? Especially if you're just using the more basic C++ features (no template (ab)use in particular).
Meanwhile the C builds done in UNIX workstations (Aix, Solaris, HP-UX) for our applications back in 2000, were taking about 1 hour per deployment target, hardly blazing fast.