From: rmswierczek@gmail.com (Robert Swierczek)
Subject: [TUHS] Non-US Unix Activities
Date: Mon, 10 Apr 2017 01:40:43 -0400 [thread overview]
Message-ID: <CAAFR5pZF=rnrEW5d_NnmEQAmyuXPTVY1UC94U5X9vhRfZUgd8A@mail.gmail.com> (raw)
In-Reply-To: <dc34dda495cb2b31347b7b55ded7b9de1aef52a0@webmail.yaccman.com>
> (Funny how this conversation makes me feel like one of a few surviving
> members of a tribe speaking a soon to be dead language...)
I think there is a beautiful simplicity to B code as a high level
assembler or universal machine language. The lack of types is closer
to the machine since a CPU generally does not enforce types on memory
or register cells.
Adding types to B (to create C) was an excellent design choice,
however another choice would have been to keep it type-less. Operator
forms would explicitly encode the appropriate type (such as unsigned
right shift >>> in Java, or floating point add #+ in BCPL.)
Pointer dereference and increment symbols would also need size
annotation (perhaps char and word forms would suffice.)
It is interesting to ponder such a language as a universal target for
higher level language compilers, or as a specialized language for OS
and device driver development.<div
id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br />
<table style="border-top: 1px solid #D3D4DE;">
<tr>
<td style="width: 55px; padding-top: 13px;"><a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon"
target="_blank"><img
src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif"
width="46" height="29" style="width: 46px; height: 29px;" /></a></td>
<td style="width: 470px; padding-top: 12px; color: #41424e;
font-size: 13px; font-family: Arial, Helvetica, sans-serif;
line-height: 18px;">Virus-free. <a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link"
target="_blank" style="color: #4453ea;">www.avast.com</a>
</td>
</tr>
</table><a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1"
height="1"></a></div>
next prev parent reply other threads:[~2017-04-10 5:40 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
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 [this message]
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='CAAFR5pZF=rnrEW5d_NnmEQAmyuXPTVY1UC94U5X9vhRfZUgd8A@mail.gmail.com' \
--to=rmswierczek@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).