Community
Participate
Working Groups
I created a subclass of Mylyn's AbstractRepositoryConnector, which apparently has .class attributes that maintain the argument names (and shows up as such in the byte-code view). The generated methods all used argument names of the form 'arg0,arg1' etc. It would be nice if in those situations the argument names could be guessed from the compiled class if the source/JavaDoc isn't available.
Moving to JDT/UI.
We use the parameter names provided by IMethod.getParameterNames(). I think the idea of using the class files attributes is very good and I suggest that the algorithm of getParameterNames is extended to do this. Moving to jdt.core.
Martin, this is already done. The problem is that for abstract methods there is no Code attribute and therefore there is no debug information we could use to retrieve the parameter names. Alex, if you look at the abstract methods in the class file editor, you will see that they have parameter named arg0, arg1,... If you define a method stub for a method from the superclass that contains some code, you should get the expected parameter names. OK to close?
Oh, I didn't know, great. I would say ok to close.
Yeah, it's a shame, but basically there's nothing we can do I guess. So Interfaces can't have parameter names stored in the .class file either? Bummer; interfaces and abstract classes are likely to be the two main places this is used. Let's close invalid.
Changing OS from Mac OS to Mac OS X as per bug 185991
