From: rminnich@gmail.com (ron minnich)
Subject: [TUHS] Unix stories, Stephen Bourne and IF-FI in C code
Date: Mon, 09 Jan 2017 15:59:00 +0000 [thread overview]
Message-ID: <CAP6exY+nZ7BZUX0v4HZ=K3gb52dF9OJRryyApwbR6Gv6byP+UA@mail.gmail.com> (raw)
In-Reply-To: <201701091545.v09FjlXE027448@freefriends.org>
On Mon, Jan 9, 2017 at 7:47 AM <arnold at skeeve.com> wrote:
> I remember the Bournegol well; I did some hacking on the BSD shell.
>
> In general, it wasn't too unusual for people from Pascal backgrounds to
> do similar things, e.g.
>
> #define repeat do {
> #define until(cond) } while (! (cond))
>
*was* not unusual? This kind of stuff is still everywhere. In fact there's
probably more of it each month. It seems to be especially popular in "high
level" languages like C++ but you see tons of it in kernels too.
Some of the worst cpp abuse I've seen is in C++ in fact. One reason I'm
glad Go has no preprocessor.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170109/da690d5f/attachment.html>
next prev parent reply other threads:[~2017-01-09 15:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 2:30 Norman Wilson
2017-01-09 3:31 ` Steve Johnson
2017-01-09 15:30 ` Marc Rochkind
2017-01-09 15:45 ` arnold
2017-01-09 15:59 ` ron minnich [this message]
2017-01-09 16:03 ` Clem Cole
2017-01-10 18:44 ` Lawrence Stewart
2017-01-09 18:48 ` Derek Fawcus
2017-01-09 20:35 ` Steve Johnson
2017-01-10 12:24 ` Tony Finch
2017-01-11 6:00 ` Brantley Coile
-- strict thread matches above, loose matches on Subject: below --
2017-01-10 13:50 Noel Chiappa
2017-01-10 4:40 Rudi Blom
[not found] <mailman.1.1484013601.5032.tuhs@minnie.tuhs.org>
2017-01-10 3:11 ` Paul McJones
2017-01-09 1:06 Doug McIlroy
2017-01-09 2:18 ` Random832
2017-01-08 20:37 Walter F.J. Mueller
2017-01-08 21:12 ` Larry McVoy
2017-01-08 21:26 ` Dave Horsfall
2017-01-08 21:54 ` Kay Parker
2017-01-08 23:14 ` Adam Sampson
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='CAP6exY+nZ7BZUX0v4HZ=K3gb52dF9OJRryyApwbR6Gv6byP+UA@mail.gmail.com' \
--to=rminnich@gmail.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).