try catch finally

I found a weird situation. I changed the name of a Property Key for a User Setting. My code worked in the simulator but crashed on the getValue() call on a real device.

After several attempts to figure it out... for grins, I went into Garmin Connect Mobile and opened the Settings function, and hit SAVE. Then cycled the power on the real device and the data field worked!! So, something was corrupted in the Storage. I imagine this might be a common repeatable bug related to this scenario - changing a Property Key Name?

Anyway, I want to implement a try/catch on my getValue() calls to keep this crap from happening to all the users of my data field... I've never used try/catch before. Seems like something simple like this could work:

try { getV = Properties.getValue("KeyName"); } catch( ex ) { getV = KeyNameDefault; }

I see there is also a "finally" block. It looks like finally just runs that block of code no matter what.

If so, how is this:

try { X; }

catch ( ex ) { Y; }

finally { Z; }

Any different from this:

try { X; }

catch ( ex ) { Y; }

Top Replies

SpitRider over 2 years ago +1

In the first case, finally would be executed even if the catch block was unable to handle some specific exception, in the second case - not. But in CIQ it seems to be no difference since exception here…
flocsy🤠 over 2 years ago +1

In theory the difference is that Z will not run in the 2nd case if X or Y have a return statement, while Z would run when it's in the finally block.

However a few weeks ago markw65 opened some bug related…

All Replies

0 SpitRider over 2 years ago

In the first case, finally would be executed even if the catch block was unable to handle some specific exception, in the second case - not. But in CIQ it seems to be no difference since exception here has no typization.

0 flocsy🤠 over 2 years ago

In theory the difference is that Z will not run in the 2nd case if X or Y have a return statement, while Z would run when it's in the finally block.

However a few weeks ago markw65 opened some bug related to finally, so it might not be true in 100% of the cases.

0 markw65 over 2 years ago in reply to flocsy🤠

Yes - due to the bug, there's basically no difference between try {A} catch (ex) {B} finally {C} and try {A} catch (ex) {B} {C}.

But as SpitRider noted, there is a difference if you do something like

try {
  A
} catch (ex instanceof MyException1) {
  B
} finally {
  C
}

where the behavior is that if A throws MyException, B and C execute; if A doesn't throw, then C executes, and if A throws something other than MyException, C executes, and then the exception is propagated.

0 markw65 over 1 year ago in reply to flocsy🤠

The bug was actually fixed in the 6.2.0 sdk. So now the finally block is executed no matter how you exit the try or catch (return, break, continue, throwing an exception).