From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Webbrowser
Date: Wed, 5 Feb 2003 20:19:31 -0500 [thread overview]
Message-ID: <51bc2f6c8ea871baffdc15d5d6433b51@plan9.bell-labs.com> (raw)
In-Reply-To: <77460E19-396D-11D7-8519-000A27AE643E@sockfarm.net>
Having gcc doesn't mean we like it. I have yet to
use gcc for anything -- even my recent Perl 5.8.0 port
still uses pcc, which is just a wrapper around 8c et al.
The main `benefit' of gcc seems to be that you could
compile C++ code, but you'd still be locked in the APE,
making it harder to integrate well with the rest of the system.
On a related note, I looked at links for a while today.
I did most of the work for a port, but there's a big
select loop at the heart of it that I just didn't want
to deal with cutting through. I also didn't write the
frame buffer, mouse, and keyboard code, but those
look easy once you kill off select.
In my frustration, I tried i again. No good.
Then I tried charon again. It's come along quite
a bit since the last time I used it. It seems like Charon
is still the best bet for now, though I do wish it were
easier to integrate with the rest of the Plan 9 environment.
There's just no good answer right now.
Russ
next prev parent reply other threads:[~2003-02-06 1:19 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 20:44 Keith Nash
2003-02-05 22:27 ` John Packer
2003-02-05 22:55 ` Skip Tavakkolian
2003-02-06 0:53 ` John Packer
2003-02-06 1:19 ` Russ Cox [this message]
2003-02-06 3:00 ` [9fans] GCC3.0 [Was; Webbrowser] andrey mirtchovski
2003-02-06 4:16 ` andrey mirtchovski
2003-02-06 14:24 ` David Presotto
2003-02-06 15:30 ` andrey mirtchovski
2003-02-06 17:32 ` David Presotto
2003-02-06 18:10 ` William K. Josephson
2003-02-06 18:16 ` Ronald G. Minnich
2003-02-06 18:23 ` William K. Josephson
2003-02-06 21:09 ` Ronald G. Minnich
2003-02-06 12:30 ` [9fans] Webbrowser - porting mozilla matt
2003-02-06 12:52 ` Ian Broster
2003-02-06 2:13 ` [9fans] Webbrowser Peter Bosch
-- strict thread matches above, loose matches on Subject: below --
2006-11-15 12:09 [9fans] webbrowser jackson john
2006-11-15 12:32 ` erik quanstrom
2006-11-15 17:56 ` csant
2003-02-06 15:09 [9fans] Webbrowser C H Forsyth
2003-02-06 14:22 C H Forsyth
2003-02-06 14:21 ` David Presotto
2003-02-06 0:56 okamoto
2003-02-05 22:57 C H Forsyth
[not found] <stalker@Math.Princeton.EDU>
2003-02-05 17:54 ` John Stalker
2003-02-05 19:16 ` Scott Schwartz
2003-02-05 19:56 ` Jack Johnson
2003-02-05 1:04 Joel Salomon
2003-02-05 1:42 ` andrey mirtchovski
2003-02-04 20:04 martin
2003-02-04 21:01 ` andrey mirtchovski
2003-02-05 7:36 ` Micah Stetson
2003-02-05 9:44 ` Douglas A. Gwyn
2003-02-05 10:19 ` Ian Broster
2003-02-05 17:10 ` Jack Johnson
2003-02-05 17:12 ` andrey mirtchovski
2003-02-05 17:19 ` Boyd Roberts
2003-02-05 17:53 ` Skip Tavakkolian
2003-02-06 2:36 ` Andrey S. Kukhar
2003-02-06 21:06 ` Russ Cox
2003-02-08 0:49 ` Andrey S. Kukhar
2003-02-05 10:22 ` Lucio De Re
2003-02-04 21:17 ` Skip Tavakkolian
2003-02-04 21:20 ` Scott Schwartz
2003-02-04 21:49 ` Jack Johnson
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=51bc2f6c8ea871baffdc15d5d6433b51@plan9.bell-labs.com \
--to=rsc@plan9.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).