On Sat, Jan 12, 2013 at 9:21 AM, Peter FELECAN <[email protected]> wrote: > Yann Rouillard <[email protected]> writes: > >> I found the bug. A mistake in code indentation but leading to an error in >> the execution path. > > This why, syntactically, Python throws me back in the glorious times of > FORTRAN and COBOL on punched cards in the seventh decade of the last > century... Semantically it's all right, the way back effect is lesser.
I agree with your sentiment. Personally, I'm ok with indentation as syntax but I keep coming back to the fact that Guido didn't go far enough. There is a sigil (colon) involved before indentation can increase but not before it can decrease. Had vertical spacing been made a part of the syntax as well as horizontal, this whole class of (easy to make) mistakes would be avoided. I'd argue that a blank line should have been required before the indentation level could be decreased. I wouldn't have been quite as visible as an "end" token or braces but it would help, I think. Thanks -Ben _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
