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,c984a7f4a0ab0148 X-Google-Attributes: gid103376,public From: dewar@cs.nyu.edu (Robert Dewar) Subject: Re: non key-words in xemacs to be upper case Date: 1996/08/17 Message-ID: #1/1 X-Deja-AN: 174741328 references: organization: Courant Institute of Mathematical Sciences newsgroups: comp.lang.ada Date: 1996-08-17T00:00:00+00:00 List-Id: iDavid Brown says "> I am an ADA programmer and using xemacs 19.13. The ADA-Mode of the > Xemacs formats the non key-words to the first character upper case > and the rest lower case. Our S/W development bible tolds us to write > those words completely upper case. Who can help me ?" I guess your software bible also tolds you to misspell poor old Ada's name too right? You should wonder whether your software bible should be reconsidered. It is borrowing an Ada 83 convention that by now is pretty universally considered inappropriate. You might note that this all upper case style was never explicitly recommended even for Ada 83, it was just implicitly recommended by the examples in the RM. The history of this is that only two styles were seriously considered, o Keywords in all caps, identifiers in lower case o keywords in lower case, identifiers in all caps Some readability studies showed that the second is preferable (and looking at Mike Feldman's code, which uses all capital keywords, I have to agree, I find the all caps for keywords style horrible, and it is interesting to note that although I encouraged my students to follow any style they liked, as long as it was consistent, and although they had Mike's text book, not ONE decided to capitalie keywords! However, the general agreement these days is that neither of these styles is the right choice, and that instead almost all programmers prefer all lower case keywords and identifiers either in Mixed_Case or (I think it is a minority, but a noticable one) as MixedCase, followingh the Pascal style (which is also what MS follows in their API's). So I think you should consider revising your bible (take a look at the Ada 95 RM to see that its implicit recommendation is for Mixed_Case identifiers).