On Sat, 2013-04-27 at 19:46 +0100, Robert Stoll wrote:
> I agree with Amaury.
> Although, it is rather smelly code to use try/catch as control flow
> instrument, in some situations it is clearer to do it this way.
> I think the new construct would be especially useful if one just wants to
> log e
I agree with Amaury.
Although, it is rather smelly code to use try/catch as control flow
instrument, in some situations it is clearer to do it this way.
I think the new construct would be especially useful if one just wants to
log errors (no further exception handling is necessary) as shown in pr
I like the idea but would prefer another control structure such as
CreateTryCatchBlockForEverySingleLine (should be shorter though) rather than
continue.
The continue keyword is confusing in my opinion. And I would say it should
be for every single statement whereupon a statement is defined by eit
