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: 109fba,d95b511473b3a931 X-Google-Attributes: gid109fba,public X-Google-Thread: 103376,d95b511473b3a931 X-Google-Attributes: gid103376,public X-Google-Thread: 1014db,d95b511473b3a931 X-Google-Attributes: gid1014db,public From: dewar@cs.nyu.edu (Robert Dewar) Subject: Re: Language Choice and Coding style Date: 1996/06/23 Message-ID: #1/1 X-Deja-AN: 161814319 references: <4qjvk5$e93@mujibur.inmind.com> organization: Courant Institute of Mathematical Sciences newsgroups: comp.lang.ada,comp.lang.c,comp.lang.c++ Date: 1996-06-23T00:00:00+00:00 List-Id: "It is fundamentally an issue of writing and detecting word breaks and what reads easiest. I suspect that using _ to separate words doesn't work well because in many cases it is hard to read -- especially when printing with very little leading between lines. I tried both styles (once I had lower case characters available) and simply found that the squashedTogetherStyle reads better. Not to mention that the use of the shift key is easier for a touch typist than constantly hitting the _ key." First, the underline used as a break character should be printed ON the base line, NOT in the underline position, many fonts are defective in this respect. Second, I think convenience of the typist is monumentally unimportant, and not a criterion that should be used in discussions of how code should be layed out.