Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Help with Indexer Bug



On Mon, Oct 14, 2013 at 11:46 AM, Joseph Henry <Joseph.Henry@xxxxxxx> wrote:

Sergey,

 

Do you have any idea what the implementation on this would look like?


You can probably follow the example of some of the existing indexer preferences. Do you have more specific questions?

 

I would really like to go ahead and add this into our companies version of eclipse ASAP.

 

I am not sure if my solution fixes the problem 100% of the time.

 

Thanks,

Joseph.


-sergey 

 

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Corbat Thomas (tcorbat@xxxxxx)
Sent: Monday, October 07, 2013 1:51 AM


To: CDT General developers list.
Subject: Re: [cdt-dev] Help with Indexer Bug

 

> Ideally there should be two preferences. One is a switch controlling whether files with include guards are indexed multiple times or not, Another, which takes effect when headers with include guards are indexed only once, provides a list of headers that are indexed multiple times despite the include guards.

+1

 

That sounds reasonable. In this way we have a simple option for enabling/disabling the more time-consuming part, which does not need much configuration overhead. And an advanced option for users who need it.

 

Regards

Thomas

 

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Sergey Prigogin
Sent: Sonntag, 6. Oktober 2013 20:04
To: CDT General developers list.
Subject: Re: [cdt-dev] Help with Indexer Bug

 

Ideally there should be two preferences. One is a switch controlling whether files with include guards are indexed multiple times or not, Another, which takes effect when headers with include guards are indexed only once, provides a list of headers that are indexed multiple times despite the include guards.

 

-sergey 

 

On Fri, Oct 4, 2013 at 7:44 PM, Nathan Ridge <zeratul976@xxxxxxxxxxx> wrote:

> I would personally like to see a preference to make it possible to disable this optimization. It could be left on by default but at least it will be possible for small and medium-sized projects to get more a more accurate index. Would that be acceptable?

+1

I can see different users falling on different sides
of this tradeoff between accuracy and performance.

Regards,
Nate

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

 


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev


Back to the top