From: Brantley Coile <brantley@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] structure allocation.
Date: Wed, 8 Mar 2006 07:11:24 -0500 [thread overview]
Message-ID: <b0f382d20ab889de0487c28f07666445@coraid.com> (raw)
In-Reply-To: <225d545abee6717eec8ffe272836f235@collyer.net>
> I was implicitly referring to C compilers. Heck, Pascal had packed
> data in the early 1970s, possibly even the late 1960s.
The first Pascal compiler became operational in 1970, on a CDC 6400.
For those born after Nixon, the CDC 6000 series was a 60 bit word
addressable machine. That explains the packed keyword.
Implementing a recursive programing language on a machine that stores
the return address of a procedure call in the first word of the
procedure was a trick. The speed of the original Pascal compiler on
the CDC machine wasn't that good. I used the compiler at the
University of Georgia in the late 1970's. Software to talk to our
packet network was written in it.
The packed keyword is still in the Pascal spec, but was dropped in Modula-2,
and Oberon.
next prev parent reply other threads:[~2006-03-08 12:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 2:30 erik quanstrom
2006-03-07 2:37 ` geoff
2006-03-07 3:00 ` erik quanstrom
2006-03-07 3:11 ` Russ Cox
2006-03-07 4:13 ` geoff
2006-03-07 15:41 ` Ronald G Minnich
2006-03-07 15:53 ` C H Forsyth
2006-03-08 0:06 ` erik quanstrom
2006-03-08 2:21 ` Ronald G Minnich
2006-03-08 2:50 ` geoff
2006-03-08 4:10 ` Bruce Ellis
2006-03-08 4:37 ` Russ Cox
2006-03-08 4:55 ` Bruce Ellis
2006-03-08 5:03 ` Russ Cox
2006-03-08 5:05 ` Bruce Ellis
2006-03-08 5:09 ` Russ Cox
2006-03-08 5:12 ` Bruce Ellis
2006-03-08 12:11 ` Brantley Coile [this message]
2006-03-07 17:47 ` Bakul Shah
2006-03-07 9:23 ` Charles Forsyth
2006-03-07 11:54 ` erik quanstrom
2006-03-07 13:55 ` jmk
[not found] ` <000501c641de$afc905d0$14aaa8c0@utelsystems.local>
2006-03-07 14:21 ` "Nils O. Selåsdal"
2006-03-07 14:30 ` uriel
2006-03-07 14:43 ` Russ Cox
2006-03-07 14:48 ` C H Forsyth
2006-03-08 0:28 ` erik quanstrom
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=b0f382d20ab889de0487c28f07666445@coraid.com \
--to=brantley@coraid.com \
--cc=9fans@cse.psu.edu \
/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).