Bugzilla – Full Text Bug Listing
| Summary: | [Refactoring] Introduce Call Tree | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Tools] PTP | Reporter: | Gustavo Rissetti <gustavorissetti> | ||||
| Component: | Photran.Refactoring Engine | Assignee: | Jeffrey Overbey <com-eclipse-dot-org> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P2 | CC: | com-eclipse-dot-org, gustavorissetti, marianomendez | ||||
| Version: | 6.0.3 | ||||||
| Target Milestone: | 8.0 | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Thanks a lot! Sorry it took me so long to get to these. I'm finally getting new contributions in for the Juno release. Can you please confirm that 1. you wrote 100% of the code without incorporating content from elsewhere or relying on the intellectual property of others, 2. you have the right to contribute the code to Eclipse, and 3. you have included the EPL license header in all source files? (In reply to comment #1) > Thanks a lot! Sorry it took me so long to get to these. I'm finally getting > new contributions in for the Juno release. > > Can you please confirm that > > 1. you wrote 100% of the code without incorporating content from elsewhere or > relying on the intellectual property of others, > > 2. you have the right to contribute the code to Eclipse, and > > 3. you have included the EPL license header in all source files? I confirm that I wrote 100% of the code without incorporating content from elsewhere or relying on the intellectual property of others, and I have the right to contribute the code to Eclipse, and I have included the EPL license header in all source files. I have committed this to master in order to meet the Juno feature freeze. Code review/testing/string externalization/documentation are pending. Closed for Juno; documentation pending. Thanks! |
Created attachment 191862 [details] Source code of the refactoring and a small example (.rar file) With this refactoring, a call tree is added at the beginning of each scope of the source code to facilitate the understanding of it for future maintenance activities. With the call tree, is known in advance which subroutines are called and we also know the number of line of code where the call is made. The source code is attached, as a figure with a small example of using this refactoring (IntroduceCallTreeRefactoring.rar).