[TUHS] Non-US Unix Activities
scj at yaccman.com
Mon Apr 10 08:45:49 AEST 2017
My memory is clearly that B did not use line numbers. However, it
did report line numbers for errors. The 'ed' command had an 'n'
command that would number the lines of the file -- I think this was a
result of an early customer for Unix being the patent department -- at
the time, patents had to have exactly 50 lines on each page with no
blanks and the lines had to be numbered... When writing about a
program, it was handy to include line numbers so the document could
refer more easily to lines in the program, but they weren't fed to the
(Funny how this conversation makes me feel like one of a few surviving
members of a tribe speaking a soon to be dead language...)
----- Original Message -----
"Alec Muffett" <alec.muffett at gmail.com>
"Random832" <random832 at fastmail.com>
<tuhs at minnie.tuhs.org>
Sun, 9 Apr 2017 12:03:13 +0100
Re: [TUHS] Non-US Unix Activities
On 9 April 2017 at 07:34, Random832 <random832 at fastmail.com >
> I've posted a few images at
> Username "iy7" spattered around the text, was Alan Cox.
> I suppose the most notable thing is use of asterisk, where C coders
> 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.
There are mentions of line numbers
in https://www.bell-labs.com/usr/dmr/www/btut.pdf  so perhaps they
are a compiler convenience for diagnostics?
 mailto:random832 at fastmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the TUHS