From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] making emalloc a library function
Date: Sun, 7 Mar 2004 15:05:08 -0800 [thread overview]
Message-ID: <14bfed15c83bd4a72d9bcc0407e39ee7@collyer.net> (raw)
In-Reply-To: <345297dba3bd4c579598a90b9a7e9a06@plan9.ucalgary.ca>
> TPOP was the first to mention emalloc (not that it wasn't used before)
Actually emalloc was mentioned in publications at least as early as
1984, in The UNIX Programming Environment.
next prev parent reply other threads:[~2004-03-07 23:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 11:32 Einar Karttunen
2004-03-07 12:56 ` David Presotto
2004-03-07 15:37 ` andrey mirtchovski
2004-03-07 17:06 ` Rob Pike
2004-03-07 17:25 ` Einar Karttunen
2004-03-07 16:47 ` andrey mirtchovski
2004-03-07 23:05 ` Geoff Collyer [this message]
2004-03-07 23:10 ` boyd, rounin
2004-03-08 10:26 ` Douglas A. Gwyn
2004-03-07 18:45 ` 9nut
2004-03-07 18:48 ` 9nut
2004-03-07 19:39 ` boyd, rounin
2004-03-07 19:34 ` boyd, rounin
2004-03-08 10:25 ` Douglas A. Gwyn
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=14bfed15c83bd4a72d9bcc0407e39ee7@collyer.net \
--to=geoff@collyer.net \
--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).