Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: commits@harmony.apache.org
Date: Tue, 17 Mar 2009 22:33:34 -0000
Message-ID: <20090317223334.23339.32926@aurora.apache.org>
Subject: [Harmony Wiki] Trivial Update of "Google Summer Of Code 2009 Projects
 Proposals" by AndrewCornwall

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Harmony Wiki" for change notification.

The following page has been changed by AndrewCornwall:
http://wiki.apache.org/harmony/Google_Summer_Of_Code_2009_Projects_Proposals

The comment on the change is:
Found another case in switch where explicit values would be nice

------------------------------------------------------------------------------
  || '''Title''' || '''Extend VMTT bytecode assembler''' ||
  || '''ASF Project''' || Apache Harmony http://harmony.apache.org ||
  || '''Keywords''' || Java, tools, vmtt||
- || '''Description''' || VMTT is a bytecode assembler used to test the Apache Harmony VM and class library. For this task, you would extend it in several ways: adding real labels (so one could write jsr loop instead of jsr -5), adding flexibility to emit more bad classes (specifying padding for tableswitch/lookupswitch, allowing double/long constant pool entries without a subsequent constant pool entry), allowing for mixed asm and bin in methods, allowing for insertion of binary data in other places (such as the constant pool), warning users of possible errors (such as bad code_length for a given code array (configurable)), and fixing existing defects. If legal approval is available, you might extend VMTT to read the JASM format as well.||
+ || '''Description''' || VMTT is a bytecode assembler used to test the Apache Harmony VM and class library. For this task, you would extend it in several ways: adding real labels (so one could write jsr loop instead of jsr -5), adding flexibility to emit more bad classes (specifying padding and values explicitly for tableswitch/lookupswitch, allowing double/long constant pool entries without a subsequent constant pool entry), allowing for mixed asm and bin in methods, allowing for insertion of binary data in other places (such as the constant pool), warning users of possible errors (such as bad code_length for a given code array (configurable)), and fixing existing defects. If legal approval is available, you might extend VMTT to read the JASM format as well.||
  || '''Possible Mentors''' || Andrew Cornwall ||
  || '''Status''' || Unassigned ||