Anonymous user
Talk:Letter frequency: Difference between revisions
m
→typos and misspellings: added r-o-t (rule of thumb). -- ~~~~
(→typos and misspellings: added more comments about program corrections. -- ~~~~) |
m (→typos and misspellings: added r-o-t (rule of thumb). -- ~~~~) |
||
Line 63:
==typos and misspellings==
Rather than point out typos and/or misspellings (and hoping that the original author notices the critique and corrects), I believe it is quite acceptable and more than that, expedient to just correct the typo or misspelling as long as it's a comment (in a program) or withing a "talk" page --- if the error is an obvious one. If there's a doubt, don't change it. It's harder to tell if there's an error when the wrong word is used (was it intentional?). If I'd bothered to complain about everybody's bad spelling, typos, or wrong word use, I'd never get any real work done. The few I did correct, I make sure it's the only thing I did on that update, so other people (especially the original poster) can see what was changed. And even then, I did the Rosetta Code update with trepidation and consternation. -- [[User:Gerard Schildberger|Gerard Schildberger]] 22:24, 25 July 2012 (UTC)
Changing program code or (input) data is much more probematic. General rule of thumb: don't.
Some programmers use misspelled words like '''kount''' (instead of count) for variable names intentionaly for whatever reasons. I also use misspelled words like Ka-razy (for crazy) at times in the comment portions; sometimes these attempts at humor may be hard to discern. There is a fine line between humor and ... not humor. -- [[User:Gerard Schildberger|Gerard Schildberger]] 22:17, 25 July 2012 (UTC)
| |||