From: toby@telegraphics.com.au (Toby Thain)
Subject: [TUHS] Non-US Unix Activities
Date: Sun, 9 Apr 2017 12:57:34 -0400 [thread overview]
Message-ID: <a798bb2d-36d7-4791-f94b-6861557a9a46@telegraphics.com.au> (raw)
In-Reply-To: <CAFWeb9Ln3c_hvDfrK3YgqBbwb3GJw9uhadrL6TM23=bxkS_a7w@mail.gmail.com>
On 2017-04-09 7:03 AM, Alec Muffett wrote:
>
> On 9 April 2017 at 07:34, Random832 <random832 at fastmail.com
> <mailto:random832 at fastmail.com>> wrote:
>
> > I've posted a few images at https://dropsafe.crypticide.com/article/12714
> <https://dropsafe.crypticide.com/article/12714>
> > Username "iy7" spattered around the text, was Alan Cox.
> >
> > I suppose the most notable thing is use of asterisk, where C coders would
> > expect backslash? And the lack of types.
>
> Are those BASIC-style line numbers?
>
>
> I honestly can't remember; I think it was the Aberystwyth sysadmin (Rob
> Ash) who write a B prettifier (the cited BTIDY) but I can't remember
> whether B as a language used/ignored line numbers, or if this was just a
> prettyprint thing.
Looks like something added in printing and not in the source.
Mercifully, B doesn't use line numbers.
--T
>
> There are mentions of line numbers
> in https://www.bell-labs.com/usr/dmr/www/btut.pdf
> <https://www.bell-labs.com/usr/dmr/www/btut.pdf> so perhaps they are a
> compiler convenience for diagnostics?
>
> -a
> --
> http://dropsafe.crypticide.com/aboutalecm
> <http://dropsafe.crypticide.com/aboutalecm>
next prev parent reply other threads:[~2017-04-09 16:57 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 22:22 [TUHS] A decision Warren Toomey
2017-04-06 20:08 ` Josh Good
2017-04-06 20:32 ` Kurt H Maier
2017-04-06 21:23 ` Aram Hăvărneanu
2017-04-06 21:46 ` Josh Good
2017-04-07 11:56 ` Steffen Nurpmeso
2017-04-07 12:20 ` William Corcoran
2017-04-07 14:05 ` Andru Luvisi
2017-04-07 15:09 ` Kurt H Maier
2017-04-07 15:23 ` Larry McVoy
2017-04-07 15:25 ` ron minnich
2017-04-07 20:25 ` Josh Good
2017-04-09 5:57 ` Michaelian Ennis
2017-04-06 23:09 ` [TUHS] Non-US Unix Activities Warren Toomey
2017-04-07 5:15 ` Dave Horsfall
2017-04-07 19:56 ` Dave Horsfall
2017-04-07 8:44 ` Alec Muffett
2017-04-07 9:32 ` Robert Swierczek
2017-04-07 10:24 ` Alec Muffett
2017-04-07 11:35 ` jsteve
2017-04-07 16:09 ` Alec Muffett
2017-04-09 6:34 ` Random832
2017-04-09 11:03 ` Alec Muffett
2017-04-09 16:57 ` Toby Thain [this message]
2017-04-09 19:20 ` Random832
2017-04-10 13:06 ` Tim Bradshaw
2017-04-09 22:45 ` Steve Johnson
2017-04-10 5:40 ` Robert Swierczek
2017-04-10 13:10 ` Tim Bradshaw
2017-04-07 17:57 ` Robert Swierczek
2017-04-07 18:24 ` Toby Thain
2017-04-07 20:23 ` Robert Swierczek
2017-04-07 20:53 ` Toby Thain
2017-04-07 21:51 ` Robert Swierczek
2017-04-07 22:08 ` Steve Johnson
2017-04-07 22:36 ` Larry McVoy
2017-04-07 22:01 ` Alec Muffett
2017-04-08 17:28 ` Lawrence Stewart
2017-04-07 10:40 ` Lars Brinkhoff
2017-04-07 12:09 ` Tim Bradshaw
2017-04-07 12:25 ` jsteve
2017-04-07 13:55 ` tfb
2017-04-07 14:36 ` George Ross
[not found] <mailman.729.1491557525.3779.tuhs@minnie.tuhs.org>
2017-04-07 14:29 ` Arrigo Triulzi
2017-04-07 23:31 Richard Tobin
2017-04-08 10:57 ` Tim Bradshaw
2017-04-08 11:13 ` Jason Stevens
2017-04-08 9:46 Berny Goodheart
2017-04-08 10:28 ` Jason Stevens
2017-04-08 14:31 Doug McIlroy
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=a798bb2d-36d7-4791-f94b-6861557a9a46@telegraphics.com.au \
--to=toby@telegraphics.com.au \
/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).