Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Rename refactoring question

Hi Sergey,
Mike is right, the implementation of the rename refactoring is defensive in that it searches for all occurrences of the
name as text and tries to analyze how the name is used. This allows to propose potential matches for names in inactive code and in macro definitions and also for names that cannot be resolved for whatever reason.
 
This behavior can certainly be made optional.
 
Markus.


From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Mike Kucera
Sent: Monday, May 17, 2010 8:49 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Rename refactoring question
Importance: Low

I think it does the text search to catch uses of the identifier in inactive code blocks.

Mike Kucera
Java JIT Compiler for System z
IBM Toronto
mkucera@xxxxxxxxxx

Inactive hide details for Sergey Prigogin ---05/17/2010 02:45:44 PM---Does anybody know the rationale for using text search as Sergey Prigogin ---05/17/2010 02:45:44 PM---Does anybody know the rationale for using text search as opposed to index-based one in rename refactoring? The slowness of the


From:

Sergey Prigogin <eclipse.sprigogin@xxxxxxxxx>

To:

"CDT General developers list." <cdt-dev@xxxxxxxxxxx>

Date:

05/17/2010 02:45 PM

Subject:

[cdt-dev] Rename refactoring question




Does anybody know the rationale for using text search as opposed to index-based one in rename refactoring? The slowness of the test search makes rename refactoring unusable on large projects. See http://bugs.eclipse.org/bugs/show_bug.cgi?id=313027 for additional details.

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



Back to the top