I guess the point could be "where do you draw the line": you can break and continue in Python, but you cannot goto. Some people, so it seems ;-) , would like to see gotos in Python whereas other think breaks and continues should be excluded ...;
Regards, Philippe Steve Holden wrote: > Philippe C. Martin wrote: >> I do not want to pollute the debate but: >> >> -) I remember a software QA managanager responsible for "C" coding rules >> also not allowing us to use 'break', 'continue', or 'return' (in the >> middle of a function). >> > And I once worked (back in the 1970's) in a software shop where "because > procedure calls are slow in PL/1" we had to write them so each procedure > ended with a GOTO to a specific label variable. You would call these > monstrosities in the following way: > > MyProcReturn = DoneIt; > GOTO MyProc; > DoneIt: > ... > > Horrendous. I lasted about five months and then couldn't take the > ignorance and idiocy any longer. They refused to believe that a > recursive function could ever be useful in the real world (but then, if > you only have a hammer ...) > > regards > Steve -- http://mail.python.org/mailman/listinfo/python-list
