Avoiding compilation cascades
From: Bil Kleb (Bil.Kleb_at_NASA.Gov)
Date: 09/24/04
- Next message: Peng Yu: "Link Lapack with C/C++"
- Previous message: Elizabot v2.0.2: "Re: Re Bruce digest, volume 2453261"
- Next in thread: Jan Vorbrüggen: "Re: Avoiding compilation cascades"
- Reply: Jan Vorbrüggen: "Re: Avoiding compilation cascades"
- Reply: Daniel Grimwood: "Re: Avoiding compilation cascades"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 24 Sep 2004 13:11:12 -0400
In Metcalf et al's new 95/2003 Explained book, there
is a nifty appendix entitled, "Avoiding Compilation Cascades".
The solution has to do with severing some of the connections
between the .mod file and the corresponding source file. This
is accomplished (in part) by using compiler options that either
only produce a .mod file or do not produce any .mod file.
However, I am worried about portability of this solution: Do all
compilers provide such options?
I have seen evidence that other groups avoid compilation
cascades by creating the equivalent of C header files. These
header files contain only module interfaces and are included
by their respective modules. The inter-module dependencies
are then tied to these interface files and not the full module.
Thus, when a given module is changed but it's interface remains
unchanged, only the altered module needs to be recompiled and
not ever module that may use it.
Regards,
-- Bil Kleb, Hampton, Virginia http://fun3d.larc.nasa.gov
- Next message: Peng Yu: "Link Lapack with C/C++"
- Previous message: Elizabot v2.0.2: "Re: Re Bruce digest, volume 2453261"
- Next in thread: Jan Vorbrüggen: "Re: Avoiding compilation cascades"
- Reply: Jan Vorbrüggen: "Re: Avoiding compilation cascades"
- Reply: Daniel Grimwood: "Re: Avoiding compilation cascades"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|