The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Richard Tobin <richard@inf.ed.ac.uk>
To: Caipenghui <Caipenghui_c@163.com>, tuhs@tuhs.org
Subject: Re: [TUHS] c's comment
Date: Fri,  7 Dec 2018 15:01:25 +0000 (GMT)	[thread overview]
Message-ID: <20181207150125.D600B2283C8E@macaroni.inf.ed.ac.uk> (raw)
In-Reply-To: Caipenghui's message of Fri, 07 Dec 2018 04:27:41 +0000

> Why can't c language comments be nested?

For comments that really are comments, what would be the point?

For comments that are really removal of code - commenting out - there
is a better mechanism, #if (or #ifdef), which does nest.

-- Richard

-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.


             reply	other threads:[~2018-12-07 16:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-07 15:01 Richard Tobin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-12-07  4:27 Caipenghui
2018-12-07  8:31 ` G. Branden Robinson
2018-12-07  9:53   ` Caipenghui
2018-12-07 14:06   ` Michael Kjörling

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181207150125.D600B2283C8E@macaroni.inf.ed.ac.uk \
    --to=richard@inf.ed.ac.uk \
    --cc=Caipenghui_c@163.com \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).