On Sunday 04 June 2006 01:27 am, Tracy R Reed wrote:
> Gabriel Sechan wrote:
> > The problems are an order fo magnitude worse in Python. In other
> > languages, so long as he only changes indentation there will be no
> > errors. In Python, that alone will fuck things up.
>
> A missing break will fuck things up just as surely. Why do you think so
> many editors have brace matching?
>
> > The fact there's a work around doesn't excuse it as a language flaw.
>
> What's the workaround for mismatched braces in your favorite language?
> There probably isn't one. You are just screwed. You've got a "language
> flaw" and nothing you can do about it.
Not true. Simply knowing that braces are mismatched is a good start
toward fixing the code.
Sigh, I can see braces. My syntax sensitive editor (vi) makes them
obvious.
I have done a little bit of coding in Python. After just a short
while tabbing seemed as natural as braces to me.
That is not the issue. Writing with tabs for braces is easy.
The problem is one missed move, one misplaced indention, is
harder to find than a missed brace. I cannot see the missed indention.
Ultimately my model is my first natural language, English. No braces!
This biases me toward Python. If you read my posts you will find
I use indention more than most folks.
But I still prefer braces. And yes, it is a religious issue. One of my few.
Braces are not NECESSARY. But they are convenient. If one is missing
it is far easier to tell that it is missing.
How do you best find a missing indention?
BobLQ
PS. A common error is a control code in the source that causes some
invisible effect ... The first time you encounter such an error you can
spend a huge amount of time looking for the invisible error which does
not show up in your editor. Perhaps this is just "old programmer ramble."
Sigh*sigh ... first year quantum mechanics
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
