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: 109fba,ea99940253996e3e X-Google-Attributes: gid109fba,public X-Google-Thread: 103376,ea99940253996e3e X-Google-Attributes: gid103376,public X-Google-Thread: 108717,ea99940253996e3e X-Google-Attributes: gid108717,public X-Google-Thread: f43e6,ea99940253996e3e X-Google-Attributes: gidf43e6,public X-Google-ArrivalTime: 2003-10-03 15:09:59 PST From: "Kevin Morenski" Newsgroups: comp.software-eng,comp.programming,comp.lang.c++,comp.lang.ada References: <2cfd1a4e.0309252032.3e3c0a1a@posting.google.com> <863cefjy6l.fsf@strudel.futureapps.de> <86ad8i7d1d.fsf_-_@huldreheim.huldreskog.no> <8665j66u8z.fsf@huldreheim.huldreskog.no> Subject: Re: Spell-checking source code (Was: ISO Studies of underscores...) Date: Fri, 3 Oct 2003 18:04:44 -0400 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 NNTP-Posting-Host: 207-99-6-58.static.nac.net Message-ID: <3f7df3af_2@nntp2.nac.net> X-Trace: nntp2.nac.net 1065218991 207-99-6-58.static.nac.net (3 Oct 2003 18:09:51 -0400) Path: archiver1.google.com!news2.google.com!newsfeed.stanford.edu!cyclone.bc.net!newsfeed.telusplanet.net!newsfeed.telus.net!news3.optonline.net!newshosting.com!news-xfer2.atl.newshosting.com!newspeer.monmouth.com!newspeer1.nwr.nac.net!nntp2.nac.net Xref: archiver1.google.com comp.software-eng:33 comp.programming:322 comp.lang.c++:675 comp.lang.ada:177 Date: 2003-10-03T18:04:44-04:00 List-Id: > // Number of misspelled words fuond so far > int noErorsInTetx = 0; > > I want to spell-check this such that I get notified both on "fuond" > for "found", "Erors" for "Errors" and "Tetx" for "Text". They are all, > after all, words in natural language, and it should be possible to > spell-check them automatically. Let's say you had a variable named "tHTa," for example. With respect to your concept, this would be a misspelling of the word "that." Now, a lot of programmers--myself included--use letters to represent certain things in variable names. tHTa could mean "type HTa" or anything else a programmer could think of. How could a program possibly differentiate between conventions in the naming of variables? It's much simpler to check the spelling of comments...programmers have developed so many conventions for making their lives easier; a spell checker on variable names just adds one more problem to overcome. kevin