Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 343904

Summary: [Refactoring] Move Subroutine Or Function To Module
Product: [Tools] PTP Reporter: Gustavo Rissetti <gustavorissetti>
Component: Photran.Refactoring EngineAssignee: 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: Future   
Hardware: PC   
OS: Linux   
Whiteboard:
Bug Depends on:    
Bug Blocks: 382437    
Attachments:
Description Flags
Source code of the refactoring and a small example (.rar file) none

Description Gustavo Rissetti CLA 2011-04-26 15:59:11 EDT
Created attachment 194099 [details]
Source code of the refactoring and a small example (.rar file)

With this refactoring is possible to move subroutines and functions of a certain scope for a existing module in order to have access to the extracted code in any scope that uses the module with the USE command. If there are PARAMETER variables used only in subroutines or functions moved, they are also moved into the module. The source code of the refactoring, as an example of use are in the attached file
(MoveSubroutineOrFunctionToModuleRefactoring.rar).
Comment 1 Jeffrey Overbey CLA 2012-03-01 00:17:20 EST
Thanks a lot!  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:24:47 EST
(In reply to comment #1)
> Thanks a lot!  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:13 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:32:49 EDT
I had to temporarily disable this in 8.0.0 due to Bug 382437, but we can definitely re-enable it in a later 8.0.x release.

Closing this since it's committed for Juno.   Thanks!