From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 108717,ea99940253996e3e X-Google-Attributes: gid108717,public X-Google-Thread: 103376,ea99940253996e3e X-Google-Attributes: gid103376,public X-Google-Thread: 109fba,ea99940253996e3e X-Google-Attributes: gid109fba,public X-Google-Thread: f43e6,ea99940253996e3e X-Google-Attributes: gidf43e6,public X-Google-ArrivalTime: 2003-10-03 04:57:13 PST Path: archiver1.google.com!news2.google.com!newsfeed.stanford.edu!news.uchicago.edu!yellow.newsread.com!netaxs.com!newsread.com!feed3.newsreader.com!newsreader.com!ngpeer.news.aol.com!newsfeed1!bredband!uio.no!newsfeed1.e.nsc.no!nsc.no!nextra.com!news2.e.nsc.no.POSTED!53ab2750!not-for-mail Sender: leifm@huldreheim.huldreskog.no Newsgroups: comp.software-eng,comp.programming,comp.lang.c++,comp.lang.ada Subject: Spell-checking source code (Was: ISO Studies of underscores...) References: <2cfd1a4e.0309252032.3e3c0a1a@posting.google.com> <863cefjy6l.fsf@strudel.futureapps.de> From: Leif Roar Moldskred Message-ID: <86ad8i7d1d.fsf_-_@huldreheim.huldreskog.no> User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii NNTP-Posting-Host: 80.212.67.67 X-Complaints-To: news-abuse@telenor.net NNTP-Posting-Date: Fri, 03 Oct 2003 13:57:12 MEST X-Trace: news2.ulv.nextra.no 1065182232 80.212.67.67 Date: 03 Oct 2003 13:53:34 +0200 Xref: archiver1.google.com comp.software-eng:27 comp.programming:275 comp.lang.c++:555 comp.lang.ada:148 Date: 2003-10-03T13:53:34+02:00 List-Id: "Mike Bandor" writes: > I was once told by a TRW employee that on one particular project they had a > coding standard that used underscores in lieu of running the names together. > One of their "measures" of readability was to take copy of the code, remove > the underscores, and run it through a spell checker. If it made it through > the spell checker, it was deemed "readable". This touches on one of my pet annoyances with development tools today: no way to easily spell-check your code. In my opinion, a development environment should at the very _least_ let you easily spell-check all the text in comments, and preferably the individual words in variable and function names (whether the words are separated by mixed case, hyphens or underscores.) Unfortunately, nobody else seems to mind. *sighs* Oh well, spell-checkers are overrated anyway. -- Leif Roar Moldskred