[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] indexer boost library
|
I can confirm that completion has problems with templates, and certainly
with iterators (not just of the boost variety). We have tons of iterators
in our code and completion doesn't work on any of them (that I've found yet).
I haven't let the full indexer run since I tried it and at 15 minutes it
was only 3% complete. So I killed it and switched to the fast indexer
which finished in a minute or two.
Kudos on the new, fast indexer - it's much better than before.
Thanks,
Larry.
Dave West wrote:
I have a really large project so I've been trying to cut down the work the CDT indexer has to do on it by selectively reducing my source path to the minimum I can get away with. While the full indexer is pretty slow, it seems to work much better on my project: I think maybe because we have a mix of C and C++ code and perhaps the fast indexer is getting confused on the preprocessor directives, but I'm only guessing on this. For instance, some of our headers contain:
#ifdef __cplusplus: I'm thinking the fast indexer can't handle the fact that these change depending on whether the current compilation unit is a .c or a .cpp file.
Yes I've noticed it doesn't do very well completing iterators either, though the iterators I've tried so far mostly had boost shared_ptrs in them :-)
I'm pretty new to using the CDT, overall it's very impressive, I'm looking forward to updates in the future that iron out some of these issues.
Cheers
----- Original Message ----
From: Doug Schaefer <DSchaefer@xxxxxxx>
To: CDT General developers list. <cdt-dev@xxxxxxxxxxx>
Sent: Thursday, 2 August, 2007 4:04:11 PM
Subject: RE: [cdt-dev] indexer boost library
I think we still have issues with templates in 4.0. I'm sure that's what
you're running into. I've always wanted this to work with iterators too. I'm
not sure if there's a bug open on it or not.
BTW, how's the performance of the full indexer in this? Unfortunately, the
template issue is with what's stored in the index and both the full and fast
indexer share that. The full indexer just gives a more accurate parse but
with a huge performance penalty when adding what it can to the index.
Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, http://cdtdoug.blogspot.com
