Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
AW: [cdt-dev] Indexer Documentation

Hello Markus,
Thx for the answer. But now I have one more final (hopefully) question:

Is the header file preprocessed (ifdef and macros are resolved) before it is parsed or is the complete (meta)data that is contained in the file parsed.

If I have understood your answer (see below) correctly the header file is preprocessed (by using a certain macro value combination defined in one certain file and through cmd line params) before parsed. 
This can lead to a wrong PDOM if the header is parsed only once but it is included from several files that are defining different macro value combinations.

Greetings Marko

-----Urspr√ľngliche Nachricht-----
Von: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Schorn, Markus
Gesendet: Donnerstag, 21. Februar 2008 10:21
An: CDT General developers list.
Betreff: RE: [cdt-dev] Indexer Documentation

Fast Indexer vs. Full Indexer:

Both indexers index exactly the same set of files. The difference is,
that the
fast indexer avoids parsing headers more than once. Depending on how
header files are written this may not be the right thing to do. The full
parses a header that is included from a different source file for a
second time. 

Usually you want to use the Fast Indexer, you pay a large performance
when using the Full Indexer. 

> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx 
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Keluna IR
> Sent: Wednesday, February 20, 2008 6:33 PM
> To: CDT General developers list.
> Subject: Re: [cdt-dev] Indexer Documentation
> Importance: Low
> I am also looking for the same.
> Thanks
> K.N
> On 2/13/08, Tomljenovic Marko (G2/PJ-PMT2) 
> <Marko.Tomljenovic@xxxxxxxxxxxx> wrote:
> > Hello,
> >
> > Does anybody know if there is a description available which 
> parts of a 
> > c/h file is indexed by the FullIndexer or the FastIndexer?
> >
> > Greetings Marko
> >
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
cdt-dev mailing list

Back to the top