NetNews Usenet Archive 1992 #27/NN_1992_27.iso/spool/comp/lang/pascal/6726

Internet Message Format | 1992-11-19 | 1.7 KB

Path: sparky!uunet!utcsri!skule.ecf!torn!nott!cunews!revcan!software.mitel.com!kim!kim
From: [e-mail] (Kim Letkeman)
Newsgroups: comp.lang.pascal
Subject: Re: Comments on Turbo (Borland) Pascal 7.0?
Message-ID: <[e-mail]>
Date: 19 Nov 92 13:27:29 GMT
References: <[e-mail]>
    <[e-mail]>
Sender: [e-mail]
Organization: MITEL Public Switching, Kanata, Ontario, Canada
Lines: 24
In-reply-to: [e-mail]'s message of 18 Nov 92 17:43:35 GMT

In article <[e-mail]> [e-mail] (James Hague) writes:

| I have seen this feature in Borland C++ 3.1 and it has me wondering.
| I think that having comments and code in different colors is a great
| idea.  But I can't figure out why anyone in their right mind would
| want to have constants, keywords, and identifiers in different
| colors.  People made a big ruckus over Modula-2's forced "IF a = b
| THEN" syntax, because it draws attention to keywords (similar to
| emphasizing puncutation over sentence content, in many people's
| opinion).

I used to favour mixed case programming, but I was introduced to all
lower case code about 7 years ago and I violently dislike anything
else now because of the distracting clutter.

Interestingly, though, I love the hilighting in TPW 1.5 and BCC 3.1. I
don't go hog-wild on colour, prefering the more subtle bolding of
keywords and greying of strings and blueing of comments. But these
things alone make source code so easy to read. One catches the
comments immediately, but can equally easily ignore them and just read
the code. In one colour code, embedded comments cannot help but
distract.
--
Kim Letkeman    [e-mail]