Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 340907 - [Refactoring] Introduce Call Tree
Summary: [Refactoring] Introduce Call Tree
Status: CLOSED FIXED
Alias: None
Product: PTP
Classification: Tools
Component: Photran.Refactoring Engine (show other bugs)
Version: 6.0.3   Edit
Hardware: PC Linux
: P2 enhancement (vote)
Target Milestone: 8.0   Edit
Assignee: Jeffrey Overbey CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-24 16:30 EDT by Gustavo Rissetti CLA
Modified: 2012-06-12 16:49 EDT (History)
3 users (show)

See Also:

Attachments
Source code of the refactoring and a small example (.rar file) (133.41 KB, application/rar)
2011-03-24 16:30 EDT, Gustavo Rissetti CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gustavo Rissetti CLA 2011-03-24 16:30:52 EDT 
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).
Comment 1 Jeffrey Overbey CLA 2012-03-01 00:15:46 EST 
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?
Comment 2 Gustavo Rissetti CLA 2012-03-01 07:21:48 EST 
(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.
Comment 3 Jeffrey Overbey CLA 2012-05-07 16:04:03 EDT 
I have committed this to master in order to meet the Juno feature freeze.

Code review/testing/string externalization/documentation are pending.
Comment 4 Jeffrey Overbey CLA 2012-06-12 16:49:35 EDT 
Closed for Juno; documentation pending.  Thanks!