|
You know how sometimes you need to change the name of an attribute? For whatever reason, the meaning of the attribute has shifted a little with time, and now it would just be better from a clarity standpoint to rename the thing. For example, I just had to change an attribute from "state" to "type". Well, if you use the "refactor" option in the JDT, it will give you an option to change the setter and getter. And if you select that option, the IDE will in turn go and find all the embedded references to the getter and setter and allow to change them as well. So now an operation that used to take at the least a few minutes to change the name, regen the setter and getter, then manually fix all the errors that popped up, and often took much lnoger especially when you screwed one up and only found out about it later during debugging, can now be done in a matter of seconds. This now means that it's entirely reasonable to make those sorts of changes, which are very important during the formative stages of a class hierarchy in order to make sure the method names are intuitive. Thanks, JDT team! Excellent job! Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.