CloneSet6471


Previous CloneSetNext CloneSetBack to Main Report
Clone
Mass
Clones in
CloneSet
Parameter
Count
Clone
Similarity
Syntax Category
[Sequence Length]
3320.960statement_sequence[2]
Clone AbstractionParameter Bindings
Clone Instance
(Click to see clone)
Line CountSource Line
Source File
13447
plugins/org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/flow/FlowAnalyzer.java
23660
plugins/org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/flow/FlowAnalyzer.java
32962
plugins/org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/flow/FlowAnalyzer.java
Clone Instance
1
Line Count
3
Source Line
447
Source File
plugins/org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/flow/FlowAnalyzer.java

                GenericSequentialFlowInfo info = createSequential(node);
                // first process right and side and then left hand side.
                info.merge(rhs, fFlowContext);


Clone Instance
2
Line Count
3
Source Line
660
Source File
plugins/org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/flow/FlowAnalyzer.java

                GenericSequentialFlowInfo info = createSequential(node);
                // first process value and then name.
                info.merge(value, fFlowContext);


Clone Instance
3
Line Count
2
Source Line
962
Source File
plugins/org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/flow/FlowAnalyzer.java

                        // Normally we should do this in the parent node since the write access take place later.
                        // But I couldn't come up with a case where this influences the flow analysis. So I kept
                        // it here to simplify the code.
                        GenericSequentialFlowInfo result = createSequential(node);
                        result.merge(info, fFlowContext);


Clone AbstractionParameter Count: 2Parameter Bindings

// Normally we should do this in the parent node since the write access take place later.
// But I couldn't come up with a case where this influences the flow analysis. So I kept
// it here to simplify the code.
GenericSequentialFlowInfo  [[#variable60fad440]]= createSequential(node);
 [[#variable60fad440]].merge( [[#variable60fad3e0]], fFlowContext);
 

CloneAbstraction
Parameter Bindings
Parameter
Index
Clone
Instance
Parameter
Name
Value
11[[#60fad440]]
info 
12[[#60fad440]]
result 
13[[#60fad440]]
info 
21[[#60fad3e0]]
rhs 
22[[#60fad3e0]]
info 
23[[#60fad3e0]]
value