9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Howard Trickey" <howard@research.bell-labs.com>
To: <9fans@cse.psu.edu>
Subject: [9fans] purpose of APE
Date: Fri, 27 Apr 2001 09:07:16 -0400	[thread overview]
Message-ID: <EPEOIODEGHAONLDKOGLHKEAACAAA.howard@research.bell-labs.com> (raw)
In-Reply-To: <200104262032.QAA22251@augusta.math.psu.edu>

It is interesting to me that the "purpose of APE" has become to allow
compiling legacy and external programs.  When Andrew Hume and I made APE
originally, the purpose was different.  It was a time when some of the
researchers in our center were actively maintaining Research Unix, while
others were doing Plan 9, and many of us had reasons to work on both
systems.  APE was a viewed as a way of writing the programs we cared about
so that they could be compiled with no change on all of the systems in our
center.  Now clearly, APE on Unix was easy to do and a first class way of
writing programs, while on Plan 9, the mapping is sometimes a bit tortured
(especially signals, select(), and some of the permission stuff), so APE on
Plan 9 is a hack, but it did serve its purpose.

I agree that the current use of APE is indeed to compile legacy and external
programs. But if that were the original goal, it would have been different:
there would have been a more kitchen-sink-union-all-the-Unixes feel to it
(ugly, ugly) so that monstrosities like autoconf would work (and it would
have infected Plan 9 --- especially the system directory conventions ---
more than any of us would have liked).

- Howard Trickey
howard@research.bell-labs.com



  reply	other threads:[~2001-04-27 13:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-26 19:42 [9fans] the declaration of main() Russ Cox
2001-04-26 20:32 ` Dan Cross
2001-04-27 13:07   ` Howard Trickey [this message]
2001-04-26 22:03 ` Boyd Roberts
2001-04-27  9:13 ` 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=EPEOIODEGHAONLDKOGLHKEAACAAA.howard@research.bell-labs.com \
    --to=howard@research.bell-labs.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).