Community
Participate
Working Groups
This feature shall add refactoring support to CDT by making use of the refactoring framwork of JDT. Furthermore by doing so, the plan is to provide an AST rewrite facility that may also be reused for quick-fixes, code formatting or other operations modifying the source code.
Created attachment 14920 [details] first plan of intent The document describes a scenario of extending CDT whith refactoring capabilities and shall serve as the foundation for further discussions.
the attached PDF seems to be corrupt!
Created attachment 14929 [details] The LaTex source of the document The pdf works for me (I had to download it and then open the downloaded file). I appached the LaTex source of the file...
Created attachment 14930 [details] first plan of intent second try to upload pdf.
Great interest so far! As with other bugs of this variety, I am assigning to Markus as owner.
Something is still wrong with the PDF file, even if separately downloaded. I was able to view it using xpdf on Linux, but unable to view it using Adobe's reader for Windows (AcroRd32.exe 4.0, 5.0, or 6.0). BTW, the TEX file is twice as long as it needs to be; it repeats itself at line 226.
Created attachment 14935 [details] The LaTex source of the document The pdf works for me (I had to download it and then open the downloaded file). I appached the LaTex source of the file...
The problem latex file is repeated seems to be a bug in bugzilla. I reattached the file and when I download it, it gets repeated after a line: Content-Type: text/plain What would be the best format for such a document?
Created attachment 14995 [details] Proposal (html)
Created attachment 14996 [details] Proposal (ms-word)
From the document: > The core of the text search of the eclipse platform is found in an > internal package. Shall we ask for a public interface to it, or is > it acceptable to access the internal part? I would raise a feature request on the platform to gain legitimate access to text search engine.
Regarding packaging/modules: Configuring a parser is not an act limited to the refactoring framework. Several other CDT features also do this work. While I am indifferent as to whether or not refactoring goes into its own plugin or into the cdt.ui plugin, I believe that this extension point (as you have described it) belongs more in the cdt.core.
Created attachment 15092 [details] Updated Proposal (html) Added an analysis of the proposed refactorings
Created attachment 15093 [details] Updated Proposal (ms-word) Added an analysis of the proposed refactorings
Created attachment 15245 [details] + AST requirements (html) Added a list of requirements towards the AST.
Created attachment 15247 [details] + AST requirements (ms-word)
Created attachment 15405 [details] JDT Inline Constant Refactoring Walkthrough Here is a walkthrough that I did while debugging JDT's Inline Constant refactoring. It provides a very interesting insight into how JDT's AST is used to perform semantic checking and how JDT's search and AST is used along with an ASTRewriter and ASTRewriterAnalyzer to create text edits to accomplish changes and even uses a Reformatter to make sure the changes look pretty. In the end, this looks like a great way, although complex, to do refactoring. How we accomplish this with C/C++, with preprocessing and other goodies, needs to be a road carefully travelled.
The rename refactoring was implemented in 3.0, returning the rest to the inbox.
*** This bug has been marked as a duplicate of bug 181493 ***
