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.

>I am trying to speak English, sorry if I am not successfull;)
>It doesn't mean it is a bad practice for someone wrote somewhere that it is a bad practice. I think the reverse.
>Cetin
>
>>I forgot at the moment who wrote "Code Complete", but I believe there was a statement there to not use multiple returns.
>>
>>It is considered bad programming practice in pure programming.
>>
>>
>>>We can argue for years and it wouldn't change the fact that multiple returns code is easier to follow.
>>>Cetin