Related articles |
---|
symbol database for C++ compiler khoury@club-internet.fr (khoury) (2001-02-23) |
Re: symbol database for C++ compiler joachim_d@gmx.de (Joachim Durchholz) (2001-02-25) |
Re: symbol database for C++ compiler broeker@physik.rwth-aachen.de (Hans-Bernhard Broeker) (2001-02-25) |
Re: symbol database for C++ compiler s355171@student.uq.edu.au (Benjamin Johnston) (2001-02-25) |
Re: symbol database for C++ compiler ucapjab@ucl.ac.uk (Jonathan Barker) (2001-03-01) |
From: | Hans-Bernhard Broeker <broeker@physik.rwth-aachen.de> |
Newsgroups: | comp.compilers |
Date: | 25 Feb 2001 10:57:35 -0500 |
Organization: | Aachen University of Technology (RWTH) |
References: | 01-02-119 |
Keywords: | C++, symbols |
Posted-Date: | 25 Feb 2001 10:57:35 EST |
khoury <khoury@club-internet.fr> wrote:
[...]
> here, the compiler has to parse all windows.h to notice that DWORD =
> long, and we know it is a long time for large projects (for
> instance, when using STL !)
If rumors and memory serve me well, here, MS VC++ is supposed to do
exactly that, already. The feature is usually called "incremental
compilation" by the marketeers, as it's meant to only recompile stuff
that really has changed, or was affected by changes elsewhere in the
project.
But using this on templates like in the C++ STL is an altogether
different game, as a template is not self-contained. It'll have to be
recompiled again each time you use it with a different parameter type,
which (assuming template recompilation issues have been handled
earlier), would mean every single time you compile it at all.
--
Hans-Bernhard Broeker (broeker@physik.rwth-aachen.de)
Return to the
comp.compilers page.
Search the
comp.compilers archives again.