Personally, i am very liberal with my lasts/breaks/returns/gotos.
There is definitely something to be said for strictness. From a theoretical
point of view, the code flows better. For example, it is easier to diagram
and easier to debug. If i write code for the company i work for, i follow
their rules, which usually means only one return statement in a sub/function
and no lasts/breaks in my loops. The word 'goto' is considered profane.
>From a practical point of view, this sort of strict adherence to an abstract
philosopy can take away from the efficiency of the program and make it more
cumbersome to write.
David's words are wise:
q/Use your judgement based on the problem... don't stick to one philosophy
or the other "just because"./
Well said.