@bstorer said:
If you advocate a rule, it might help to understand the actual reasoning behind the rule instead of clinging to it blindly.
Why all the animosity? I am not trying to force you to use single-exit point, I prefer it for my own coding. I believe it makes code MORE readable, less error prone, and much easier to refactor. If you don't agree with me so be it. I don't think I have ever had an issue where my methods had to use an insane amount of nesting to achieve single-exit point. I am not sure where that belief comes from.
I understand that single exit point is more a structured programming idea rather than OO as OO languages have constructs that render it mostly impossible to achieve 100% of the time (i.e. exception handling). However, that doesn't stop me from using at when at all possible and I would say 95% of the time it is acheivable. If I run across a situation where I have to/need to use multiple exit points I don't lose sleep over it.