The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: scj@yaccman.com (Steve Johnson)
Subject: [TUHS] // comment in C++
Date: Wed, 08 Feb 2017 15:39:13 -0800	[thread overview]
Message-ID: <10bc76e824e441f031dc541ab4d50a51bfb89638@webmail.yaccman.com> (raw)
In-Reply-To: <201702081817.v18IHShk031735@freefriends.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]

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...

Steve

----- Original Message -----
From: arnold@skeeve.com
To:<tuhs at minnie.tuhs.org>, <rminnich at gmail.com>
Cc:
Sent:Wed, 08 Feb 2017 11:17:28 -0700
Subject:Re: [TUHS] // comment in C++

 ron minnich <rminnich at gmail.com> wrote:

 > I've always wondered if this was done in honor of JCL, as sort of a
riff on
 > the dd command. Anyone know?
 >
 > ron

 I'm fairly certain it was originally in BCPL.

 You could just drop a note to Bjarne Stroustrup and ask. :-)

 Arnold

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170208/d8a7449b/attachment.html>


  reply	other threads:[~2017-02-08 23:39 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08 18:06 ron minnich
2017-02-08 18:08 ` A. P. Garcia
2017-02-08 18:17 ` arnold
2017-02-08 23:39   ` Steve Johnson [this message]
2017-02-08 23:52     ` Dave Horsfall
2017-02-09  2:11       ` Corey Lindsly
2017-02-09  2:46         ` Dave Horsfall
2017-02-09  2:53           ` Corey Lindsly
2017-02-09  4:38           ` Warner Losh
2017-02-09  2:47       ` Steve Nickolas
2017-02-09  4:55         ` Steve Johnson
2017-02-09 11:59           ` Michael Kjörling
2017-02-09 21:56             ` Dave Horsfall
2017-02-10  0:17               ` Dan Cross
2017-02-10  1:58                 ` Dave Horsfall
2017-02-10  2:46                   ` Nemo
2017-02-10  2:49                     ` Dave Horsfall
2017-02-10  9:30                   ` arnold
2017-02-10  9:19               ` arnold
2017-02-09 12:18           ` Brantley Coile
2017-02-09 13:31             ` Nick Downing
2017-02-08 22:45 ` Greg 'groggy' Lehey
2017-02-08 22:50   ` Ron Natalie
2017-02-08 23:22     ` Greg 'groggy' Lehey
2017-02-09 12:12     ` Michael Kjörling
2017-02-09 12:26       ` Lars Brinkhoff
2017-02-09 14:37         ` Random832
2017-02-09 14:49           ` Random832
2017-02-09 12:31       ` Paul Ruizendaal
2017-02-09 13:07         ` Steffen Nurpmeso
2017-02-08 22:51   ` ron minnich
2017-02-08 23:22     ` Greg 'groggy' Lehey
     [not found] <mailman.204.1486594285.3779.tuhs@minnie.tuhs.org>
2017-02-09  0:03 ` Paul McJones
2017-02-09  2:28   ` Marc Rochkind
2017-02-09 13:11   ` Tony Finch
2017-02-09 14:44 Noel Chiappa
2017-02-09 16:51 ` Steffen Nurpmeso
2017-02-09 19:36   ` Steffen Nurpmeso
2017-02-09 21:14 Doug McIlroy
2017-02-10 17:39 ` Steffen Nurpmeso

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=10bc76e824e441f031dc541ab4d50a51bfb89638@webmail.yaccman.com \
    --to=scj@yaccman.com \
    /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).