I have an I2C device that wants two inputs: a denominator and a numerator. Both are written to separate addresses, so no actual calculation (numerator/denominator
) is done. The problem with this is that a divide by zero could occur on the I2C device, so a divide by zero error needs to be checked for. Ideally, exactly the same thing would happen if the dividing were done by the java code.
At the moment, I've bodged an unused variable that does the division, but I'm worried it'll get optimized out:
public void setKp(int numerator, int divisor)
{
int zeroCheck = numerator / divisor;
//... doesn't use zeroCheck
}
Surely there's a better way!
Something like:
Do this:
ArithmeticException is the exception which is normally thrown when you divide by 0.
There are two ways you could do this. Either create your own custom exception class to represent a divide by zero error or throw the same type of exception the java runtime would throw in this situation.
Define custom exception
Then in your code you would check for a divide by zero and throw this exception:
Throw ArithmeticException
Add to your code the check for a divide by zero and throw an arithmetic exception:
Additionally, you could consider throwing an illegal argument exception since a divisor of zero is an incorrect argument to pass to your setKp() method:
You should not throw an ArithmeticException. Since the error is in the supplied arguments, throw an
IllegalArgumentException
. As the documentation says:Which is exactly what is going on here.