From: scj@yaccman.com (Steve Johnson)
Subject: [TUHS] Non-US Unix Activities
Date: Fri, 07 Apr 2017 15:08:48 -0700 [thread overview]
Message-ID: <1e89d5607378028b7e5c493f8389e51327587033@webmail.yaccman.com> (raw)
In-Reply-To: <CAAFR5pbo0qbEpymF=oZj-ccXxK6gc8X1R73EKuWUFqb-+n86cw@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2195 bytes --]
At AT&T, the evolution from B to C was quite smooth, as was the
evolution of C itself. Most B programs were converted to "nb" (the
first C incarnation) by hacking on the character strings and putting
in some types where needed. It wasn't a big deal. So I'd be
surprised if there were substantial B programs that survived.
One lesson learned that I've never forgotten is how smooth it is to
evolve a language using the following process:
* Announce that the change is coming and explain why
* Change the compiler to accept both the old and new syntax
* Produce a simple warning message when the old syntax was used, but
make it still work
* Produce a more complicated, verbose message, but still make it work
* Produce a message that says "After date xxxx, the old stuff won't
work any more"
* On the date, change the warning to fatal, but keep recognizing the
old syntax and emit "Error: You used the old xxx, change to the new
one"
* Eventually, stop recognizing the old syntax and remove the message.
Dennis was a master at this strategy, so things like the otherwise
painful evolution of changing =+ to += went well.
Steve
----- Original Message -----
From: "Robert Swierczek" <rmswierczek@gmail.com>
To:"Toby Thain" <toby at telegraphics.com.au>
Cc:<tuhs at minnie.tuhs.org>
Sent:Fri, 7 Apr 2017 17:51:03 -0400
Subject:Re: [TUHS] Non-US Unix Activities
>
> Yes, there's always SOME way to avoid it, but obviously
significantly more
> work. Just depends what the priorities are... Preserving fanfold
seems like
> a strange priority, wouldn't it be more practical bound book-like
anyway?
>
> Or, similar to your suggestion, load it into a compatible printer
(so that
> it can be sprocket fed), with some kind of takeup spool, then form
feed
> pages through, snapping each one between feeds.
>
Fully agree! If there is anything I can do to help get that online
(in whatever form) let me know.
Are there any other surviving examples of B code from that era in
this
ballpark of complexity?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170407/271b9970/attachment.html>
next prev parent reply other threads:[~2017-04-07 22:08 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
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 [this message]
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=1e89d5607378028b7e5c493f8389e51327587033@webmail.yaccman.com \
--to=scj@yaccman.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).