a112 - Try with unassigned var Topic is solved

[TheArkive]

When using Try with an unassigned var, instead of Try capturing the error for handling in Catch, it throws an error.

Is this intended?

[Helgef]

Currently this is the expected behaviour,

Enabled #Warn UseUnset by default - to be converted to a continuable error at some point.

You can turn the warning off, if you want to fix it later.

Cheers.

[TheArkive]

Ok that makes sense. Thanks!

From the point of a "best practice", would it make more sense to use #Warn to disable it, or to ensure values are initialized, or i guess (in that case) use IsSet()?

If figure this answer could easily be subjective, but just wondering what you think.

[Helgef]

I would recommend you initialise your variables. I would probably only use isset to

• detect when an optional paramter was omitted (f(p:=unset)),
• detect if an initialisation has failed. Eg in a catch or finally block.
• Perhaps also for static vars in some cases.

Cheers.