From: Nick LaForge <nicklaforge@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] LLVM for plan 9?
Date: Tue, 31 Aug 2010 13:31:56 -0800 [thread overview]
Message-ID: <AANLkTimeCx2pd4Wgfb5TjNGiggfqwHD+jE-NLZBVk2=v@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimeAJW3dCUaPDZA7-J5NgQvkN0mr3WmakZpY=Ag@mail.gmail.com>
>There's tutorials for doing so from O'Caml
[http://llvm.org/docs/tutorial/]
That looks really neat. I had watched this*:
[http://vimeo.com/14313378] weeks back, subsequently flipping through
Appel's "Modern Compiler Implementation in ML", but ultimately
deciding the book to be too boring. This, on the other hand, is
pretty inciting.
However, I still couldn't bring myself to deal with an additional
compiler as long as gcc+valgrind+qemu+vx32 continue to work.
I also wouldn't touch LLVM before all the opportunities for synergy
between lunix and Plan9 created by Golang are exhausted, and I think
there are lots of them. (Is 9Go still unfinished even?)
*Not really recommended because it is too long, though it did turn me
on to the O'Caml language.
>> Is this a trick to get C++ back on Plan9??
> was it ever?
(Completely irrelevant to people living in 2010; cfront not guaranteed
against causing brain hemorrhages)
You can see B. Stroustrup's monitor prominently displaying either 8½
or Rio on the back of "The Design and Evolution of C++" (©1994 AT&T
Bell Labs)...
And: /n/sources/extra/c++.2e.tgz
next prev parent reply other threads:[~2010-08-31 21:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 16:10 David Leimbach
2010-08-31 18:33 ` Nick LaForge
2010-08-31 19:48 ` David Leimbach
2010-08-31 21:31 ` Nick LaForge [this message]
2010-08-31 22:21 ` David Leimbach
2010-08-31 22:24 ` Nick LaForge
2010-08-31 20:56 ` EBo
2010-08-31 20:59 ` Ori Bernstein
2010-08-31 21:03 ` David Leimbach
2010-08-31 21:52 ` Bakul Shah
2010-08-31 22:21 ` David Leimbach
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='AANLkTimeCx2pd4Wgfb5TjNGiggfqwHD+jE-NLZBVk2=v@mail.gmail.com' \
--to=nicklaforge@gmail.com \
--cc=9fans@9fans.net \
/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).