[TUHS] // comment in C++
Steve Johnson
scj at yaccman.com
Thu Feb 9 14:55:21 AEST 2017
Well, personally I use // for almost all comments in C/C++. I
reserve /* */ for commenting out blocks of code. Since, for some
reason, /* */ doesn't nest, if I stick to this style life is good.
Steve
----- Original Message -----
From: "Steve Nickolas" <usotsuki at buric.co>
To:"The Eunuchs Hysterical Society" <tuhs at tuhs.org>
Cc:
Sent:Wed, 8 Feb 2017 21:47:49 -0500 (EST)
Subject:Re: [TUHS] // comment in C++
On Thu, 9 Feb 2017, Dave Horsfall wrote:
> On Wed, 8 Feb 2017, Steve Johnson wrote:
>
>> I remember some discussion about this. In reality, a C comment
really
>> requires you to type 8 characters, because putting anything
adjacent to
>> the /* or */ looks terrible. Many languages used single
characters
>> (e.g., # for make). The argument was "if you make comments
easier to
>> type, you'll get more of them in the code" (viz. the Unix
kernel). I'm
>> guessing Bjarne was aware of these discussions, although I don't
>> remember specifically that he was...
>
> My favourite C /* */ style is this:
>
> /*
> * foo
> * bar
> */
This is the way I usually write my comments, too.
> Is that what you meant? And recent C also accepts // as a comment,
which
> I use like this:
>
> /*
> * This is where we do some neat stuff.
> */
> foo();
> weird_function(); // Yes, we need to call this here...
> bar();
>
> I'm quite taken by BIND, though, which accepts
>
> /* this */
> // this
> # and this.
Unrealircd likewise accepts those 3 different types of comments.
-uso.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170208/a6dd92a5/attachment.html>
More information about the TUHS
mailing list