Andrei Alexandrescu wrote:
I mean even if ostensibly you don't want to handle errors, you still need to mind the multiple hidden exit paths in your code to achieve even the most intuitive guarantees (such as temporarily changing a global for the duration of a function). Such a style of coding blindsides old-style SESE programmers (and is the main reason for which I unrecommend SESE).

I agree. That makes sense.

Reply via email to