Re: [K3d-development] CVS release notes - K-3D 0.3.9.6 (K-3D 0.4 rc1)

[Timothy M. S. <ts...@k-...>]

Ed Millard wrote:

> In looking at the first four files in modules/core they sure seem to be
> including pretty much the same set of headers which is where you might
> get a pretty big win from a precompiled header.  
> 
> When you reach this level of sameness in a module its open to debate if
> you should even be imposing on yourself or others to figure out the
> nearly the same but slightly different set of includes.

Agreed.  In the early days we had a handful of uber-include files that 
pulled-in everything, and *that* was a slow compile.  Obviously, there 
is a fundamental tradeoff between convenience (one big master header) 
and compile-time performance (many small headers, chosen based on need). 
  I've had it in mind for awhile to find a happy medium for the 
convenience of plugin authors, I've been waiting for the dust to settle 
before deciding how to break-down the functionality.

Precompiled headers are new in gcc 3.4.  Anyone who wants to experiment 
on integrating them into the build without breaking it for the rest of 
us is welcome to do so.  Here's the official gcc 3.4 manual page:

http://gcc.gnu.org/onlinedocs/gcc-3.4.0/gcc/Precompiled-Headers.html#Precompiled%20Headers

Amusingly, the RedHat version is nearly identical, but leaves-out the 
cautionary paragraph on known crashes ;)

Cheers,
Tim