From: "ComeauAt9Fans@gmail.com" <comeauat9fans@gmail.com>
To: "lucio@proxima.alt.za" <lucio@proxima.alt.za>,
Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Cc: "9fans@9fans.net" <9fans@9fans.net>
Subject: Re: [9fans] nix at lsub
Date: Thu, 19 Apr 2012 13:09:33 -0400 [thread overview]
Message-ID: <40957748-5D32-49BC-AA46-FE94396DB788@gmail.com> (raw)
In-Reply-To: <eafec68dc4b7e0cbdc5a7925bc3cd7e0@proxima.alt.za>
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
> On Apr 19, 2012, at 12:11 PM, Lucio De Re <lucio@proxima.alt.za> wrote:
>>> We would be glad to work further on such a C++ port with anybody who
>>> can handle the Qt end of things so anybody interested in exploring
>>> such an endeavor should discuss with us.
>>
>> I have a friend who is totally sold on LLVM, but I note that it is
>> itself written in C++, so bootstrapping would be difficult (I think I
>> still have a running version of GCC 3.0,
>
> Speaking with their developers a few years ago they did not think it was a good idea/reasonably feasible.
>
> I may be biased, but still sure some general flavor of Comeau for Plan 9 could be a near term and not expensive endeavor (though it depends upon ones definition of inexpensive too I guess). And Qt definitely has its place in the world.
>
> - Greg
[-- Attachment #2: Type: text/html, Size: 2456 bytes --]
next prev parent reply other threads:[~2012-04-19 17:09 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 18:05 arnold
2012-04-19 1:37 ` hiro
2012-04-19 4:15 ` Jeff Sickel
2012-04-19 8:10 ` Charles Forsyth
2012-04-19 8:16 ` Joseph Stewart
2012-04-19 8:46 ` Charles Forsyth
2012-04-19 10:03 ` Bakul Shah
2012-04-19 10:32 ` Charles Forsyth
2012-04-19 16:36 ` Bakul Shah
2012-04-19 15:50 ` ComeauAt9Fans@gmail.com
2012-04-19 16:11 ` Lucio De Re
2012-04-19 17:09 ` ComeauAt9Fans@gmail.com [this message]
2012-04-19 17:56 ` Lucio De Re
2012-04-19 18:05 ` Comeau At9Fans
2012-04-19 18:23 ` Lucio De Re
2012-04-19 18:27 ` Lucio De Re
-- strict thread matches above, loose matches on Subject: below --
2012-04-18 16:09 arnold
2012-04-18 16:18 ` Nemo
2012-04-18 16:28 ` Charles Forsyth
2012-04-18 16:35 ` Francisco J Ballesteros
2012-04-18 17:43 ` Lucio De Re
2012-04-18 15:45 arnold
2012-04-18 15:49 ` Francisco J Ballesteros
2012-04-14 21:02 Nemo
2012-04-15 13:45 ` David Leimbach
2012-04-16 10:47 ` Francisco J Ballesteros
2012-04-16 11:02 ` Noah Evans
2012-04-16 17:23 ` Aram Hăvărneanu
2012-04-16 17:32 ` Noah Evans
2012-04-16 17:42 ` Noah Evans
2012-04-16 17:44 ` ron minnich
2012-04-16 20:53 ` Andrés Domínguez
[not found] ` <CAEAzY380ECzLQJCbNaK=QiYE6vzQpqTW3ZoakzW7EJ-WajptHg@mail.gmail.c>
2012-04-16 17:54 ` sl
2012-04-16 13:22 ` Christoph Lohmann
2012-04-16 18:04 ` Lucio De Re
2012-04-17 2:16 ` kokamoto
2012-04-17 5:53 ` andy zerger
2012-04-17 5:54 ` andy zerger
2012-04-17 7:17 ` Nemo
2012-04-17 8:41 ` kokamoto
2012-04-17 8:51 ` Francisco J Ballesteros
2012-04-17 12:22 ` Tristan
2012-04-17 18:56 ` Charles Forsyth
2012-04-17 19:13 ` Nemo
[not found] ` <charles.forsyth@gmail.com>
2012-04-18 0:26 ` kokamoto
2012-04-18 4:07 ` John Floren
2012-04-18 4:12 ` John Floren
2012-04-18 7:54 ` Francisco J Ballesteros
2012-04-18 12:27 ` Charles Forsyth
2012-04-18 12:35 ` Francisco J Ballesteros
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=40957748-5D32-49BC-AA46-FE94396DB788@gmail.com \
--to=comeauat9fans@gmail.com \
--cc=9fans@9fans.net \
--cc=lucio@proxima.alt.za \
/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).