Ya I'm pretty sure I know what I'm talking about and yes your program will work just as it is
do this and you will see how not using the else if ladder for one is time saving
two it could keep you out of trouble not using else ifs would be like not putting breaks in a switch statement
Put a break point on your first if in calculator2() function and run it in debug
if you don't know how it's good to know how so I'll say how to do it just in case
to put a break point in click to the left of the line numbers (if you don't have line numbers showing)
the far left of the code window. You should see a red dot that's your break point now press F5 (not Ctr F5) do the calculator and do the 3 number then say add on both and after you do that you will see the program stops make sure you in visual studio and push the F10 that will walk you through how the compiler reads the program and you will see the after it reads the if statement that's true it stills checks the other ifs which is pointless and could cause headaches if future programming. Now after you seen how it goes and checks all the ifs go ahead and press shift F5 to stop debugging now go and add a else before all the ifs but the first and run the debug again and watch what it does this time.
I only told you to use the else if ladder because that program would run better (not that you would notice)but to help give you a idea of what there is and what you can do. There will be times when a ladder of just ifs are necessary though. As you write programs you will see.
Using the debug can be very very helpful it shows you how the compiler is running your code.
I know I've had problems where it had different ideas on what to do then what I had in mine and I would have to run it to see what I did wrong.
