Newsgroups: comp.std.c
Path: utzoo!utgpu!watserv1!watmath!datangua
From: datangua@watmath.waterloo.edu (David Tanguay)
Subject: Re: comment style
Organization: University of Waterloo
Date: Wed, 9 Jan 91 00:35:43 GMT
Message-ID: <1991Jan9.003543.3087@watmath.waterloo.edu>
References: <613@caslon.cs.arizona.edu> <1050:Jan701:40:4791@kramden.acf.nyu.edu> <616@caslon.cs.arizona.edu> <17968:Jan804:38:1591@kramden.acf.nyu.edu>
Lines: 22

In article <17968:Jan804:38:1591@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
>No. #2 is an objective fact and #3 is a widely accepted principle of
>visual design: parallel lines are striking. Read Tufte's books.

Then Tufte is wrong, at least in this instance :-) One of the problems I
have found with C++ code is that I don't see the comments (caveat: I've not
looked at a lot of C++ code). The // looks like a letter to me (it's almost
an italic N).

>No, not when they're done correctly. When you have end-of-line comments
>there's no need for continuation characters. *All* characters are
>ignored between // and newline inclusive.

What about:

#define BLAH	stuff	// comment about BLAH
	some code here

If the newline is stripped, then "some code here" becomes part of the macro,
which seems nasty.
-- 
David Tanguay            Software Development Group, University of Waterloo