From: dot@dotat.at (Tony Finch)
Subject: [TUHS] // comment in C++
Date: Thu, 9 Feb 2017 13:11:27 +0000 [thread overview]
Message-ID: <alpine.DEB.2.11.1702091304360.23062@grey.csi.cam.ac.uk> (raw)
In-Reply-To: <C4318F2B-0041-4BDE-9885-AE3389929C38@mcjones.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
Paul McJones <paul at mcjones.org> wrote:
> > I'm fairly certain it was originally in BCPL.
> >
> > You could just drop a note to Bjarne Stroustrup and ask. :-)
>
> On page 44 of _The Design and Evolution of C++_ (Addison-Wesley, 1994),
> Stroustrup says:
>
> “However, only C, Simula, Algol68, an in one case BCPL left noticeable
> traces in C++ as released in 1985. Simula gave classes, Algol68
> operating overloading, references, and the ability to declare variables
> anywhere in a block, and BCPL gave // comments.”
>
> He says a bit more about // comments on page 93, including an example of
> how they introduced an incompatibility with C.
There's more in Stroustrup's paper for the second History of Programming
Languages conference, http://www.stroustrup.com/hopl2.pdf
See especially the prehistory section 2.1 on page 3 where he talks about
the painful tooling he was faced with in Cambridge, where Simula was nice
for program design but had a woefully slow implementation, whereas BCPL
was fast but grievously unsafe.
The quote above is repeated in the HOPL2 paper on page 12 in section 2.4.4
on "Why C?" and there's a bit more about comment syntax in section 3.3.1
on page 21.
Tony.
--
f.anthony.n.finch <dot at dotat.at> http://dotat.at/ - I xn--zr8h punycode
Wight, Portland: East or northeast 4 or 5, increasing 6 at times. Slight or
moderate, occasionally rough in Portland. Showers. Moderate or good.
next prev parent reply other threads:[~2017-02-09 13:11 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2017-02-09 21:14 Doug McIlroy
2017-02-10 17:39 ` Steffen Nurpmeso
-- strict thread matches above, loose matches on Subject: below --
2017-02-09 14:44 Noel Chiappa
2017-02-09 16:51 ` Steffen Nurpmeso
2017-02-09 19:36 ` Steffen Nurpmeso
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
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
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=alpine.DEB.2.11.1702091304360.23062@grey.csi.cam.ac.uk \
--to=dot@dotat.at \
/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).