Two design approaches to consider The essence pattern The fluent interface pattern These are both similar in intent, in that we slowly build up an intermediate object, and then create our target object in a single step. An example of the fluent interface in action would be: public class CustomerBuilder { String surname; String firstName; … Read more
Visual Assist and Visual Studio make dealing with large codebases much easier. Visual assist is good at tracking down how a class or member is used and is more effective at renaming it without false positives than search and replace.
The main alternative is: CodeRush, by DevExpress. Most consider either this or ReSharper the way to go. You cannot go wrong with either. Both have their fans, both are powerful, and both have talented teams constantly improving them. We have all benefited from the competition between these two. I won’t repeat the many good discussions/comparisons … Read more
You can simply use Apache Commons Lang: result = ObjectUtils.compare(firstComparable, secondComparable)
Yes, ReSharper does this. Right click on your solution and selection “Find Code Issues”. One of the results is “Unused Symbols”. This will show you classes, methods, etc., that aren’t used.
An Eclipse plugin that works reasonably well is Unused Code Detector. It processes an entire project, or a specific file and shows various unused/dead code methods, as well as suggesting visibility changes (i.e. a public method that could be protected or private).
I think the shortcut that you’re looking for is: Ctrl+Shift+R on Windows and Linux/Ubuntu Control+Shift+R on macOS (IntelliJ IDEA Classic keymap) Cmd+Shift+R on macOS (macOS keymap) ref: source
Google’s cppclean (links to: download, documentation) can find several categories of C++ problems, and it can now find superfluous #includes. There’s also a Clang-based tool, include-what-you-use, that can do this. include-what-you-use can even suggest forward declarations (so you don’t have to #include so much) and optionally clean up your #includes for you. Current versions of … Read more
Just use Analyze | Inspect Code with appropriate inspection enabled (Unused declaration under Declaration redundancy group). Using IntelliJ 11 CE you can now “Analyze | Run Inspection by Name … | Unused declaration”
Performance, namespace pollution etc are all secondary in my view. Ask yourself what is logical. Is the method logically operating on an instance of the type, or is it related to the type itself? If it’s the latter, make it a static method. Only move it into a utility class if it’s related to a … Read more