Re: Language Choice and Coding style

[mfinney@inmind.com]

In <dewar.835574607@schonberg>, dewar@cs.nyu.edu (Robert Dewar) writes:

>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.

Even when they are not, if the leading between lines is insufficient
then the underscore is hard to read.  Nevertheless, we generally have
to work with existing fonts and it is a common problem.  Even on 
screen.

>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. 

The convenience of the typist is not important as to SHOULD, but is
extremely relevant to IN PRACTICE and is therefore relevant as an
explanatory mechanism for the adoption of squashedText over
non_squashed_text.

And regardless of both of the above points, the squashedText
still seems to read substantially better than the non_squashed_text
so, in my opinion, the squashedText sytle is preferable.  And I
have used both -- actually, I used the non_squashed_text first
and changed over because it was more readable in my opinion
(NOT because it was more typable).