Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of weldonwjw@gmail.com designates
 64.233.166.180 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=jp042pI5/qXFbov1WF1SWtnx/pauLVnzMR0eyP9iKE1puuMatK7E5JmYvt9h5GmyIPiL55WmZfnVbX63cjMDaIQqyzfDRxQ5fhXHPzfBAYnlaYfzBdJhPOdX6H5fGFI+Hi8azaLvRXsby1Pe+JngzYY2DDCuqBBvq7dnSXVzct0=
Message-ID: <4dd1f3f00602212053p74552bfbud0d1ffe79c437d25@mail.gmail.com>
Date: Tue, 21 Feb 2006 20:53:12 -0800
From: "Weldon Washburn" <weldonwjw@gmail.com>
To: harmony-dev@incubator.apache.org
Subject: [jchevm] rough draft of Harmony Class Lib to gnu native method glue
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

 Archie, Tim,

I tried to attach a zip file but harmony-dev rejected it.  I also
tried to post the zip file to harmony/jira.  It did not work.  I will
mail the zip file to you out of band while I try to figure out how to
upload the zip file.

Sent separately is a zip file containing a first cut at gluing Harmony Clas=
s
Library to the native methods exposed by JCHEVM.   I call this glue,
"kernel_path".   So far, no mods have been made to any JCHEVM files.
All modifications to date have been to java files contained in the
Harmony Class Library (HCL) kernel directory.

We can use the above to start the debate on how files like Thread.java
should be designed.  We should also decide where to put kernel_path.
Meanwhile, I plan to build jchevm and attempt to run hello_world.java
using HCL.

Let me know what you think.


--
Weldon Washburn
Intel Middleware Products Division