home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.pascal
- Path: sparky!uunet!ornl!sunova!linac!mp.cs.niu.edu!uxa.ecn.bgu.edu!news.ils.nwu.edu!konopka
- From: konopka@ils.nwu.edu (Ray Konopka)
- Subject: Re: Comments on Turbo (Borland) Pascal 7.0?
- Message-ID: <1992Nov19.030016.13441@ils.nwu.edu>
- Sender: usenet@ils.nwu.edu (Mr. usenet)
- Nntp-Posting-Host: aristotle.ils.nwu.edu
- Organization: The Institute for the Learning Sciences
- References: <1992Nov18.131557.7438@odin.diku.dk> <1992Nov18.174335.2758@exu.ericsson.se>
- Date: Thu, 19 Nov 1992 03:00:16 GMT
- Lines: 29
-
- In article <1992Nov18.174335.2758@exu.ericsson.se> exuhag@exu.ericsson.se writes:
- >Niels Ull Jacobsen writes:
- >>
- >>1: Source code highlighting
- >>You can set it up so that all keywords are white,
- >>all user identifiers are green, all constants are black, all comments
- >>are grey and some syntactic errors are red. Of course you can change
- >>the colour set up. It may sound trivial and confusing, but I find it
- >>VERY useful - you catch a lot of typing errors as you type.
- >
- >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).
- >
- ...stuff deleted...
-
- Having keywords colorized is very useful because you can easily
- pick out mispellings while you are typing. Quoted strings are
- also colorized, which proves quite useful in finding non-terminated
- strings of text.
-
- Ray Konopka
- konopka@aristotle.ils.nwu.edu
-
-
-