I notice that this is still present in build 632. I personally see it as an annoying and potentially serious bug. Are there any plans to fix it?
N. Nathan Brown wrote: > When I add a new parameter to a method and specify a default value for the > new parameter, the value is used in all current invocations, as expected. > However, it is also used in calls to the superclass' method in overriden > methods. Surely the default behaviour should be to pass the parameter value > supplied to the overriden method through to its call to super rather than > passing a default value and ignoring the incoming value? > > Someone let me know if I'm missing something here, but I think this is a > bug. If it is meant to do this, then can we have an option on the Change > Method Signature dialog to force the refactoring to pass the value through > to super, as that's surely a valid option too. > > Regards, > N. > > _______________________________________________ Eap-bugs mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-bugs
