From: Steve Harris <scharris@worldnet.att.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Anyone working on C++ for Plan9?
Date: Fri, 11 Aug 2000 19:39:49 -0500 [thread overview]
Message-ID: <20000811193949.A1568@tiger.home.net> (raw)
Has anybody thought of porting the SmallEiffel compiler as an
alternative?
It produces C code which then is compiled by a platform's existing C
compiler.
Supposedly produces pretty efficient C code. Won't try to advocate
Eiffel as
a language (though I think it is excellent), but will say it is very
different
from C and therefore can be a lot of fun as a change of pace.
The weakest part of Eiffel is its lack of libraries (for doing
networking e.g.).
Since Plan 9 can do so many things with just read/write calls, seems
like that's
a big win for Eiffel and other weakly-libraried languages.
Just a thought, I'm not volunteering.
Steve
next reply other threads:[~2000-08-12 0:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-12 0:39 Steve Harris [this message]
2000-08-14 8:49 ` Douglas A. Gwyn
-- strict thread matches above, loose matches on Subject: below --
2000-08-11 21:34 rob pike
2000-08-11 21:49 ` Boyd Roberts
2000-08-11 20:34 Russ Cox
2000-08-11 20:56 ` Boyd Roberts
2000-08-11 0:10 Skip Tavakkolian
2000-08-11 0:15 ` Boyd Roberts
2000-08-11 19:59 ` Skip Tavakkolian
2000-08-11 19:54 ` Boyd Roberts
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=20000811193949.A1568@tiger.home.net \
--to=scharris@worldnet.att.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).