From: "rob pike" <rob@plan9.bell-labs.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Java for Plan 9?
Date: Fri, 26 Oct 2001 06:59:59 -0400 [thread overview]
Message-ID: <00c101c15e0d$5ba96b20$7bf8fea9@oemcomputer> (raw)
In-Reply-To: <vi41yjrl109.fsf@blue.cs.yorku.ca>
The problem lies mostly in the libraries. Who's going to reimplement
that enormous pile of, ahem, software.
----- Original Message -----
From: Ozan Yigit <oz@blue.cs.yorku.ca>
To: <9fans@cse.psu.edu>
Sent: Friday, October 26, 2001 5:24 AM
Subject: Re: [9fans] Java for Plan 9?
> rob@plan9.bell-labs.com (rob pike) writes:
>
>
> > That implementation artifact is a part of the existing implementations,
> > though, which complicates the porting issue.
>
> perhaps a fresh implementation is more appropriate.
>
next prev parent reply other threads:[~2001-10-26 10:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 17:06 rob pike
2001-10-26 9:24 ` Ozan Yigit
2001-10-26 10:59 ` rob pike [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-29 21:32 David Gordon Hogan
2001-10-25 11:28 Richard Miller
2001-10-24 8:44 Matt Senecal
2001-10-24 12:47 ` rob pike
2001-10-24 13:59 ` Latchesar Ionkov
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='00c101c15e0d$5ba96b20$7bf8fea9@oemcomputer' \
--to=rob@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).