Op 2005-12-06, [EMAIL PROTECTED] schreef <[EMAIL PROTECTED]>:
>> Just because a few people dislike something,
>> doesn't make it a defect.
>
> Actually, it does. Unless you're in the business of building security
> systems. Then the goals are reversed.
>
> I can accept that you like scope by indent and don't want to see any
> changes gong forward. That's your choice.
>
>
>> it's somewhat ironic that you have to cite a documented
>> source to back up your point.
>
> Somewhat. :)
>
>> Do you think that adding braces to Python will mean
>> we can remove part of the existing documentation?
>
> No, it will add a little there. Where it will cut down is the
> otherwise unending debate over the issue. Documentation is not just
> what you find on a single web page.
What I don't understand is, that most people who have a problem
with scope by indentation, want to introduce braces. I think
braces are the worst solution.
Python has clear constructs that mark where suites begin. There
is no need for an extra open brace. So if you don't want to
rely on indentation, something to mark the end of a suite
would be sufficient.
I personnaly don't like the forced indentation of python
and its lack of endmarkers for suits/blocks. I also think
it is not that a big deal. Just as I indent my code in
languages that don't enforce it, I generally put in
end markers when I program python.
In the past that was just by using comments like:
if ...:
...
#end
But lately I have been wondering about doing the following:
end = None
...
if ...:
...
end
IMO it looks better, but I'm reluctant because it suggest
some checking by the compilor, which just doesn't happen.
--
Antoon Pardon
--
http://mail.python.org/mailman/listinfo/python-list
