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: | "Joachim Durchholz" <joachim_d@gmx.de> |
Newsgroups: | comp.compilers |
Date: | 25 Feb 2001 10:52:21 -0500 |
Organization: | Compilers Central |
References: | 01-02-119 |
Keywords: | C++, performance |
Posted-Date: | 25 Feb 2001 10:52:21 EST |
khoury <khoury@club-internet.fr> wrote:
> do you know about a c++ compiler that builds a database of all
> symbols *before* compiling time, such as it knows about all
> dependencies before to open all header files.
The MSVC++ compiler does something like this (it uses a "program
database"). However, this is generally difficult to do in C++:
changing a preprocessor symbol may change the syntax of large parts of
source, making it difficult for the compiler to decide what to
invalidate after a change. This means either more recompilation than
strictly necessary, or a large and complex (and thus more buggy)
dependency tracker. This works better for languages that don't have
preprocessors on the lexical level. For example, such databases are
common and much more useful in languages like Smalltalk (where the
source is stored in the database), Java (lots of IDEs with incremental
compilation), Eiffel (also incrementally compiling).
Regards,
Joachim
Return to the
comp.compilers page.
Search the
comp.compilers archives again.