>I see your point and I use premature returns a lot in my code as well, but I still agree with the fact that it is a bad practice from the theoretical "pure" programming point of view.
>
>We had this discussion long ago with my husband (at that time just a boyfriend). I forgot the arguments used, unfortunately.
>
>Would be nice to try to repeat that conversation with him again if he still remembers.
>

OK you can catch me that I am not a computer sciences graduate but I can think, read and learn. One can convince if she/he can solidly show why it is a bad practice. If you are saying it is bad then there should be a solid reason. All I need is a solid reason.

BTW I didnit say premature return. They are mature enough, before returning (whereever you do immediately or single exit) wouldn't do anything else and return value is definitely known at that point.
Cetin