The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: rminnich@gmail.com (ron minnich)
Subject: [TUHS] dead bstj unix link on wikipedia
Date: Mon, 02 Apr 2018 22:53:29 +0000	[thread overview]
Message-ID: <CAP6exYLYyd7RytCbeq7nTNd4COu4zv_tZYzoXy0-G2Ffw+Dg5Q@mail.gmail.com> (raw)
In-Reply-To: <CANUoZoG4ZDeo-TeMPq9YeQw6uzASQekPNL3=kFTJcGhUSs6phw@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 899 bytes --]

That turned out to be the wrong paper.

I'm looking for a paper that describes the (early) dialect of C that let
you do stuff like this:

struct w {
char lo, hi;
};

int x;

char b = x.lo;

I can't find my hardcopy so was looking for a pdf.

ron

On Mon, Apr 2, 2018 at 10:36 AM David du Colombier <0intro at gmail.com> wrote:

> > anyone got a fix?
> >
> > https://en.wikipedia.org/wiki/Bell_System_Technical_Journal
> >
> > see this text
> >
> >  Ritchie, D.M.; K. Thompson (July–August 1978). "The UNIX Time-Sharing
> > System". Bell System Technical Journal. 57 (6). Retrieved 2010-10-22
>
> https://9p.io/cm/cs/who/dmr/cacm.html
>
> More generally, just replace "cm.bell-labs.com" with "9p.io".
>
> --
> David du Colombier
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180402/e7cc9661/attachment.html>


  reply	other threads:[~2018-04-02 22:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-02 16:11 ron minnich
2018-04-02 16:24 ` Leonardo Taccari
2018-04-02 17:36 ` David du Colombier
2018-04-02 22:53   ` ron minnich [this message]
2018-04-03  5:11     ` David du Colombier
2018-04-05 21:17     ` Jonathan Gevaryahu
2018-04-05 21:37 ` Jonathan Gevaryahu
2018-04-02 17:34 Noel Chiappa

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=CAP6exYLYyd7RytCbeq7nTNd4COu4zv_tZYzoXy0-G2Ffw+Dg5Q@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).