On Mon, 22 Oct 2012 07:22:18 +1100, Chris Angelico wrote: > On Mon, Oct 22, 2012 at 6:11 AM, Steven D'Aprano > <steve+comp.lang.pyt...@pearwood.info> wrote:
>>> Ahh. I totally didn't see that, I'm way too used to reading past >>> typos. >> >> As a programmer, doesn't that screw up your debugging ability? > > Reading-past-typos applies mainly to English, which is a pretty > redundant language. In code, it would only apply to variable names; with > (effectively) single words/tokens standing alone, the automatic > correction doesn't really apply. But yes, sometimes I have stared at a > piece of code for a long time without knowing why there's an error on > line X. (This is another good reason to require that all variables be > declared, incidentally. I might have a variable called "source" but not > "souce", so using the other causes an instant compile-time failure on > the exact line with the bug.) "Another" good reason? For languages without static types, what other reasons for declaring variables are there? -- Steven -- http://mail.python.org/mailman/listinfo/python-list
