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: f43e6,ea99940253996e3e X-Google-Attributes: gidf43e6,public X-Google-Thread: 109fba,ea99940253996e3e X-Google-Attributes: gid109fba,public X-Google-ArrivalTime: 2003-10-14 09:49:13 PST Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed00.sul.t-online.de!newsmm00.sul.t-online.com!t-online.de!news.t-online.com!not-for-mail From: "Jakob Bieling" Newsgroups: comp.software-eng,comp.programming,comp.lang.c++,comp.lang.ada Subject: Re: Spell-checking source code Date: Tue, 14 Oct 2003 18:46:59 +0200 Organization: T-Online Message-ID: References: <2cfd1a4e.0309252032.3e3c0a1a@posting.google.com> <863cefjy6l.fsf@strudel.futureapps.de> <86ad8i7d1d.fsf_-_@huldreheim.huldreskog.no> <86zngh5oct.fsf@huldreheim.huldreskog.no> <86r81s6elg.fsf@huldreheim.huldreskog.no> <3F830C63.1070005@crs4.it> <3F8BFCF5.6020906@crs4.it> <3f8c1a9f_2@mk-nntp-2.news.uk.tiscali.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: news.t-online.com 1066149974 05 22595 JNtwVbhVScAnT 031014 16:46:14 X-Complaints-To: usenet-abuse@t-online.de X-ID: VA08STZSge3JsUprS6ONwo0PA+gcz83ymbV9+ODOrGTtjJT85QzG67 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 Xref: archiver1.google.com comp.software-eng:20781 comp.programming:951 comp.lang.c++:2335 comp.lang.ada:840 Date: 2003-10-14T18:46:59+02:00 List-Id: "Peter Bushell" wrote: > "Jakob Bieling" wrote: > > "Jacob Sparre Andersen" wrote: > > Also, sometimes I tend to abbreviate quite a lot, so that later I > might > > not know what it stands for. In cases like those I just put a comment next > > to where I declared the variable and I can keep saving those keystrokes. > If you can't remember what it meant, pity the poor engineer who has to > maintain your code when you've gone! Having to look up a declaration every > few seconds is not acceptable. You do not have to. All declarations (loop counters etc. are an exception) are at the beginning of the function, along with possible comments. And for those identifiers where comments are necessary, I do not think it is impossible to remember them. > There is evidence* to suggest that 80% of programming is (or should be) > thinking time. Saving keystrokes is therefore not an issue. True, but it is still pretty annoying to type all kinds of variable names out (we are talking about long names, anything over 10 letters, right?) all the time you use them. The 'burden' of remembering 5 or 6 names for which you always see the abbreviations is less, in my opinion. To avoid misunderstandings, I do not approve using abbreviations for all kinds of variables. But I do find it acceptable to use my way of abbreviating (including comments) for function local variables. hth -- jb (replace y with x if you want to reply by e-mail)