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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,66bc6b039f1e005d X-Google-Attributes: gid103376,public From: Robert A Duff Subject: Re: Three simple questions Date: 2000/10/16 Message-ID: #1/1 X-Deja-AN: 682105611 Sender: bobduff@world.std.com (Robert A Duff) References: <2BED68CA963D6D55.A78776F656DA0452.75A61ED22116F1B6@lp.airnews.net> <39E47BAC.8DB1AD0B@acm.org> <86aec7tl59.fsf@acm.org> Organization: The World Public Access UNIX, Brookline, MA Newsgroups: comp.lang.ada Date: 2000-10-16T00:00:00+00:00 List-Id: Laurent Guerby writes: > kenner@lab.ultra.nyu.edu (Richard Kenner) writes: > > [...] Some would say this argues in favor of underscores not being > > significant either, so you couldn't have a disinct Roll_Control > > variable either, but "roll underscore control" sounds a lot smoother > > than saying "each cycle we set the capital r roll capital c control > > variable from the average of the lower-case r roll lower-case c > > control, lower-case r roll capital c control, and capital r roll > > lower-case c control variables"! > > Nice example ;-). I don't buy it. I find it impossible to chat about programs of any substantial size without writing them down -- that's what whiteboards are for. > As for underscores, if you put them consistently between words, you > don't even need to mention them while discussing your program. And > since Ada identifiers cannot begin with, have two consecutive or end > with an underscore, there's no problem at all. The same is true of casing -- if you use sensible conventions, case sensitivity doesn't damage talking. Eg, you might have "the type FOO", and "the variable foo". I still think case sensitivity is error prone. > Note that this issue transcend programming languages and goes up to > the more general human-computer interface field. ... Reminds of a user-interface I heard of that used the C convention, where an integer literal starting with "0" is octal. It's bad enough in a programming language, but to foist that on unsuspecting (non-programmer) users is pretty horrible. - Bob