The JLS section on unreachable code explains the rationale. Essentially, Java normally shouldn’t use conditional compilation like C routinely does with #ifdef, but there are some situations (such as debugging, and in particular backward binary compatibility) where allowing the compiler to entirely strip out code is needed, and so the specific construct if(false) is permitted … Read more
Well, your variables i and prevSpec_OilCons, if not used anywhere will be optimized away, but not your loop. So if your code looks like: static void Main(string[] args) { int[] TestRunTime = { 1, 2, 3 }; int i = 0; for (int j = 0; j < TestRunTime.Length; j++) { } double prevSpec_OilCons = … Read more
I know that Gimpel’s Lint products (PC-Lint and Flexelint) will identify unreachable code and unused / unreferenced modules. They both fall in the category of static analysis tools. I have no affiliation w/ Gimpel, just a satisfied long-term customer.
The first does not compile (you got an error), the second compiles (you just got a warning). That’s the difference. As to why Eclipse detects dead code, well, that’s just the convenience of an integrated development tool with a built-in compiler which can be finetuned more as opposed to JDK to detect this kind of … Read more
You could use a code coverage analysis tool for this and look for unused spots in your code. A popular tool for the gcc toolchain is gcov, together with the graphical frontend lcov (http://ltp.sourceforge.net/coverage/lcov.php). If you use gcc, you can compile with gcov support, which is enabled by the ‘–coverage’ flag. Next, run your application … Read more
Without looking for anything too complex: JSLint (not really a static analyzer, but if you give it your concatenated development code, you’ll see what methods are never called, at least in obvious scoping contexts) Google Closure Compiler Google Closure Linter
In Python you can find unused code by using dynamic or static code analyzers. Two examples for dynamic analyzers are coverage and figleaf. They have the drawback that you have to run all possible branches of your code in order to find unused parts, but they also have the advantage that you get very reliable … Read more
Solution: For node projects, run the following command in your project root: npx unimported If you’re using flow type annotations, you need to add the –flow flag: npx unimported –flow Source & docs: https://github.com/smeijer/unimported Outcome: Background Just like the other answers, I’ve tried a lot of different libraries but never had real success. I needed … Read more
Does the existence of such a statement in a given program mean that the whole program is undefined or that behavior only becomes undefined once control flow hits this statement? Neither. The first condition is too strong and the second is too weak. Object access are sometimes sequenced, but the standard describes the behavior of … Read more
Press Ctrl+Shift+A (in Mac Command+Shift+A) Enter “unused declar” Double-click on “Unused declaration” Settings will pop up Click on Java/Declaration redundancy/Unused declaration on the right bottom select “On the fly editor settings” untick check fields, …, check parameters. Only Check Classes should be ticked. Press OK Settings closes On the menu bar, click on Analyze / … Read more