From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] Java for Plan 9? From: "rob pike" MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-krcuwwfkrgdrnnnvxhkyixizmq" Message-Id: <20011025170624.90DB519A17@mail.cse.psu.edu> Date: Thu, 25 Oct 2001 13:06:21 -0400 Topicbox-Message-UUID: 0d454fb8-eaca-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-krcuwwfkrgdrnnnvxhkyixizmq Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit That implementation artifact is a part of the existing implementations, though, which complicates the porting issue. -rob --upas-krcuwwfkrgdrnnnvxhkyixizmq Content-Type: message/rfc822 Content-Disposition: inline Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Thu Oct 25 11:57:27 EDT 2001 Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Thu Oct 25 11:57:26 EDT 2001 Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.6.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id AC37819A25; Thu, 25 Oct 2001 11:57:11 -0400 (EDT) Delivered-To: 9fans@cse.psu.edu Received: from marvin.nildram.co.uk (marvin.nildram.co.uk [195.112.4.71]) by mail.cse.psu.edu (CSE Mail Server) with SMTP id 6D19D19A25 for <9fans@cse.psu.edu>; Thu, 25 Oct 2001 11:56:11 -0400 (EDT) Received: (qmail 14827 invoked from network); 25 Oct 2001 15:56:10 -0000 Received: from hamnavoe.gotadsl.co.uk (HELO hamnavoe) (213.208.117.150) by marvin.nildram.co.uk with SMTP; 25 Oct 2001 15:56:10 -0000 To: 9fans@cse.psu.edu Subject: Re: [9fans] Java for Plan 9? From: Richard Miller MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Message-Id: <20011025155611.6D19D19A25@mail.cse.psu.edu> Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.6 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Thu, 25 Oct 2001 12:28:19 0100 > Java's peculiar insistence that class structure be wired into the source > file structure This is just an implementation artifact; it doesn't have to be done that way. The Java language specification says (7.2): "Each host determines how packages, compilation units, and subpackages are created and stored ... The packages may be stored in a local file system in simple implementations of the Java platform. Other implementations may use a distributed file system or some form of database to store source and/or binary code." Even if classes are stored one per file, there's no insistence that file names be identical to class names. (There couldn't be, because class names can contain non-ASCII Unicode characters which many operating systems -- Plan 9 excepted! -- can't cope with.) All that's required is a mapping between them. -- Richard Miller --upas-krcuwwfkrgdrnnnvxhkyixizmq--