From: Caipenghui <Caipenghui_c@163.com>
To: tuhs@tuhs.org
Subject: [TUHS] c's comment
Date: Fri, 07 Dec 2018 04:27:41 +0000 [thread overview]
Message-ID: <1C1BB8D2-9535-4A6D-96E8-3792F14BCBAE@163.com> (raw)
Why can't c language comments be nested? What is the historical reason for language design?Feeling awkward.
Caipenghui
next reply other threads:[~2018-12-07 4:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 4:27 Caipenghui [this message]
2018-12-07 8:31 ` G. Branden Robinson
2018-12-07 9:53 ` Caipenghui
2018-12-07 14:06 ` Michael Kjörling
2018-12-07 15:01 Richard Tobin
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=1C1BB8D2-9535-4A6D-96E8-3792F14BCBAE@163.com \
--to=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).