Skip to content

Instantly share code, notes, and snippets.

@emopers

emopers/Long_BadParsingArgs

Created March 7, 2016 03:14
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save emopers/e75ddb58e73bacb5612a to your computer and use it in GitHub Desktop.
Save emopers/e75ddb58e73bacb5612a to your computer and use it in GitHub Desktop.
Download ZIP
Raw
Long_BadParsingArgs
##Unneccessary property##
Long_BadParsingArgs property (http://goo.gl/F6ygPN) would trigger violations if a String passed into Long.parseLong()
is not valid for representing a Long value. JVM will throw NumberFormatException upon receiving an invalid input,
which is exactly the same thing as what this property does. This property does not provide more useful debugging
information than JVM exception itself, nor does it provide insight into the prevention of such Exception. For all the
violations we got from monitoring with this property on 200 open source projects with passing tests are false alarm,
for which the Exceptions thrown by JVM are used to recognize the validity of inputs and well handled.
@emopers
Copy link
Author

emopers commented Mar 16, 2016

Abandoned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment