9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: baldwin@vitanuova.com
To: 9fans@cse.psu.edu
Subject: [9fans] Why not APE?
Date: Thu, 26 Apr 2001 20:13:14 -0400	[thread overview]
Message-ID: <20010427001316.C9ECC19A45@mail.cse.psu.edu> (raw)

Russ has it dead on: Plan 9 isn't attempting to be compatible with
"Standard C" and has no previous usage to be worried about.  It's
trying to come up with a clean system -- keeping old baggage around
is *not* the way to do that.  And what would be the point of the
old baggage?  Does anybody really believe that native Plan 9 would
be able to compile and run off-the-shelf Unixoid programs?  To do
that would require major damage to Plan 9.

The APE solution seems to work just fine: if you want "int main()"
and stdio and signals and tcgetattr and sockets and all that other,
err, junk, well go right ahead and use APE.  It seems to work as
well as can be expected (don't blame APE for autoconfig hell).
For heaven's sake, even X11 was compiled under it.

Now this may be a little weird, but I for one use the Inferno C libraries
to compile Plan 9 programs on Unixoid boxes.  They are sort of an inverse-APE.
They don't intend to be a complete implementation of the Plan 9 C libraries,
but they do well enough that my sundry Plan 9 programs compile and run on,
say, Solaris (like the mk and C compiler tools of Inferno do).  And I don't
have to de-Plan 9 them.

I am quite happy that the baggage of the past can be left to the side
and not intertwine itself with Plan 9 and constrain it.  If I wanted a
system that could compile and run all the "lovely" Unix programs out
there, well I'd go get FreeBSD or something.


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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-27  0:13 baldwin [this message]
2001-04-27 14:42 ` 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=20010427001316.C9ECC19A45@mail.cse.psu.edu \
    --to=baldwin@vitanuova.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).