Issue 746 in moose-technology: VerveineJ should create parameters for methods with different signatures

Status: New
Owner: ----
CC: [hidden email]
Labels: Type-Defect Priority-Medium Component-VerveineJ Milestone-4.6

New issue 746 by [hidden email]: VerveineJ should create parameters  
for methods with different signatures
http://code.google.com/p/moose-technology/issues/detail?id=746

In some cases, calls to external libraries get reified as methods with  
proper signatures, but without parameters.

I am trying to reproduce this using the following example (in  
ad_hoc/MultipleSignatures.java):

package ad_hoc;

import java.io.PrintWriter;
import java.io.StringWriter;

public class MultipleSignatures {
       
        public void callToRegularPrintStackTrace(Throwable t) {
                t.printStackTrace()
        }
       
        public void callToPrintStackTraceWithParam(Throwable t) {
                t.printStackTrace(new PrintWriter(new StringWriter()))
        }
}

I encountered a similar code in a case study. However, in this case, I  
cannot even get the parser to recognize both printStackTrace calls.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Updates:
        Labels: -Milestone-4.6 Milestone-4.7

Comment #1 on issue 746 by [hidden email]: VerveineJ should create  
parameters for methods with different signatures
http://code.google.com/p/moose-technology/issues/detail?id=746

(No comment was entered for this change.)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev