Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!clyde.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!mintaka!spdcc!ima!dirtydog!karl
From: karl@ima.isc.com (Karl Heuer)
Newsgroups: comp.std.c
Subject: Re: comment style
Message-ID: <1991Jan07.052003.13765@dirtydog.ima.isc.com>
Date: 7 Jan 91 05:20:03 GMT
References: <1991Jan04.164355.15674@sco.COM> <613@caslon.cs.arizona.edu> <1050:Jan701:40:4791@kramden.acf.nyu.edu>
Sender: news@dirtydog.ima.isc.com (NEWS ADMIN)
Organization: Interactive Systems
Lines: 23

In article <1050:Jan701:40:4791@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
>In article <613@caslon.cs.arizona.edu> dave@cs.arizona.edu (Dave P. Schaumann) writes:
>> I see no compelling reason to have //, and have heard
>> no argument for // that doesn't boil down to 'I like it that way better'.
>
>[Several arguments deleted]

My favorite is the observation that virtually all% one-line comments end with
a newline following the "*/", and virtually all% multi-line comments have
cosmetic punctuation (usually " * ") at the beginning of each line, anyway.
So it seems clear that the programmers are, at some level, *thinking* in terms
of comment-to-EOL, and it probably would have been better for the comment
syntax to have reflected that in the first place.

I don't claim this is a compelling reason, and I won't even dispute that it's
just a variant of "I like it that way better".  The fact that I first came up
with this idea, including the "//" symbol, years before I knew that BCPL and
C++ used "//" comments, will be of interest to those individuals who take an
interest in that sort of thing.

Karl W. Z. Heuer (karl@ima.isc.com or uunet!ima!karl), The Walking Lint
________
% There are a few exceptions, but I don't find *them* compelling, so there :-)