It would be VERY useful, if it could analize the usages and suggest only types, that would keep the program working exactly as before.
But this refactoring feature should apply to all type definitions, not just for return values of methods. Maybe an idea for a post-Ariadna build? Tom On Mon, 01 Jul 2002 10:26:25 +0100, Nathan Brown <[EMAIL PROTECTED]> wrote: >>> And, as the icing on the cake, is it possible to change the type of a >>> field, >>> and change its setter and getter too? >> >> No, is no refactoring to change type of a field. > >But can this be put in, please? ;) > >N. > _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
