jack: (Default)
[personal profile] jack
*sigh* There were other more funadmental problems, but instrumental in the bug was my muddling the precedence of "&" and "==". Obviously, we all make these mistakes sometimes. And I've got a lot better at avoiding minor mistakes as I've taken a more professional approach to programming.

But does everyone else (who programs) still find such typos happening?

For that matter, surely there is room for improvement in editors. Most people I know seem to use emacs, UltraEdit at work, vi if they're contrary, or Visual Studio if that's what they're using. But without going into details of which I've thought a lot, there seems a lot more that could be done to make minor errors, time spent comprehending code, etc, which eats up lots of productivity better? Surely it's the most obvious project for any programmer to want to work on?

Date: 2006-08-01 11:33 pm (UTC)
From: [identity profile] fluffymormegil.livejournal.com
That's why I tend to paranoiacally put linebreaks (using my autoindenting editor) in long parenthetical constructs at suitably locations.

Date: 2006-08-01 11:46 pm (UTC)
From: [identity profile] cartesiandaemon.livejournal.com
Again, yes... but then a statement which might be doing something conceptually simple sprawls across much screen space, and you can't see the overall outline of the function because this bit is so prominent. You have to go put it in a function or something...