what's the difference between the 2 catch statements in divide method, and




They both seem to do 2 catches, to see which ones to use....

They are both doing two catches.
The divide catches gives a more direct output error than you would get with the second catch offered with less code.

i.e for Divide
If you get a NoSuchElement error, it'll strictly go into that catch and print out that direct error (but you should probably print 'e' in your throw as well)
If you get a ArithmeticFunction error, itl'l strictly deal with arithmetic.

i.e for second:
If it gets either exception, it'll toss it to e. In this case, you could print a general throw, such as "no suitable input" and it would handle both types of exceptions, but it is less versatile.
You can make it do the same thing as the divide fx by creating an if statement for checking the instance type (NoSuch or Arithmetic), but at that point you should really just go back to using the catch offered in divide.

I wrote up a quick mock-up to help comprehend, it's in Python but you should get the gist.



Logs:


This post was edited by Candyzcanes on Oct 18 2019 11:00pm

hmmm thanks

what did you mean by this:

Printing your actual error. You're currently just posting specific cases like:
throw new ArithmeticException("no suitable input");
throw new ArithmeticException("attempt to divide by zero");

ArithmeticException is a general exception to some extent. So, at least during testing phases, you should print what the actual error is so you can make sure you know what's actually going on.
My code for that was:
print("Cant divide by 0!\nERROR: ", str(e))

(I concatenate the string that is more relevant to me and the exception)

Gotchya thanks