2011-02-25, 18:02
Hi,
I just want to let the developers know that I love the Android remote very much and have been having a great experience with it so far.
Today I checked out the source code from svn out of curiosity and tried using FindBugs on it. That's a very cool Eclipse plugin that help find out a large number of potential problems in Java source codes.
The code I'm viewing is svn 748.
For example, in SetupWizardPage1.java line 92, we're comparing a String e.getMessage() to an int HTTP_UNAUTHORIZED, which never returns true.
The program also reveals several other problems relating to possible null dereferencing, tests that always return false, or potentially inconsistent synchronization, etc.
I think using this tool and try to eliminate all the warnings is a great way of preventing dangerous bugs. I hope my suggestion is useful for the project.
Again, thanks for making one of the coolest thing I've had on my phone ^^
I just want to let the developers know that I love the Android remote very much and have been having a great experience with it so far.
Today I checked out the source code from svn out of curiosity and tried using FindBugs on it. That's a very cool Eclipse plugin that help find out a large number of potential problems in Java source codes.
The code I'm viewing is svn 748.
For example, in SetupWizardPage1.java line 92, we're comparing a String e.getMessage() to an int HTTP_UNAUTHORIZED, which never returns true.
The program also reveals several other problems relating to possible null dereferencing, tests that always return false, or potentially inconsistent synchronization, etc.
I think using this tool and try to eliminate all the warnings is a great way of preventing dangerous bugs. I hope my suggestion is useful for the project.
Again, thanks for making one of the coolest thing I've had on my phone ^^