'try' best practice?

[MoCityMM]

Was wondering if 'try..finally' and 'try..exception' is a necessary conjunction in code or one without the other is really all that is needed?

What is your coding practice with the two?

[marcov]

Was wondering if 'try..finally' and 'try..exception' is a necessary conjunction in code or one without the other is really all that is needed?

What is your coding practice with the two?

It really depends on your application field. In my current situation doing machine vision, most exceptions will kill the application anyway, and there is little to none dynamic allocation per item/transaction, so there is not much point in doing so.

In previous jobs I did webdevelopment, and then it is absolutely required to make sure an aborted request releases all its memory.

[ASerge]

Was wondering if 'try..finally' and 'try..exception' is a necessary conjunction in code or one without the other is really all that is needed?
What is your coding practice with the two?

The "try finally" construction is often used. Without it, the code even looks like a novice's. The "try except" construction is much less common, only if need to handle some exception. And by the way, these are completely different constructions in meaning, which is why I don't like the fact that they are united in some languages. They only have "try" in common.

[440bx]

What is your coding practice with the two?

I use "try/except" only when the code I'm writing is "messing" with things that don't belong to - are not managed by - my program.

I never use "try/finally".  My viewpoint on that one is, if the program is structured correctly, there will never be a need for it.