Subject: C439 JGSI Review
Resent-Date: Thu, 30 Sep 1999 23:17:29 -0400
Resent-From: Geoffrey Fox <gcf@npac.syr.edu>
Resent-To: p_gcf@npac.syr.edu
Date: Fri, 17 Sep 1999 15:45:07 +0100 (BST)
From: Mark Bull <markb@epcc.ed.ac.uk>
To: Geoffrey Fox <gcf@npac.syr.edu>

Paper no. C439
Title: Extending Java Virtual Machine with Integer-Reference
Conversion
Reviewer: Mark Bull

Overall Recommendation: Publish with minor revisions

Comments to authors:

An interesting and clearly presented paper. The English grammar needs
some attention.

section 1, para 1: Add references to Scheme and ML.

section 1, para 2, line 3: could -> can

section 1, para 4, line 7/8: statically typed program -> statically
typed programs

section 1, para 5 -> The example code for this operation is shown in
Figure 2. Of the three steps, the final step is the most problematic,
as it causes huge numbers of objects to be allocated throughout the
execution of a typical program. Generally the ....... integer
additions.  Furthermore, it creates many discarded objects which have
to be garbage collected, which results in frequent garbage collection.
Both of these effects significantly slow down program execution.

section 1, last para: add descriptions of sections 5 and 7.

section 2, para 1, list item 2: bytecode -> bytecodes

section 2.1, para 3, line 4: map descriptor type -> map the descriptor type

section 2.1, last para, line 10: is modified -> are modified

section 2.2, para 3, line 6: fit in 31 bit -> fits in 31 bits

section 2.2, last para, line 1: Using static -> Using a static

section 2.2, last para, last line: altering instruction set ->
altering its instruction set

section 2.3, line 1 after list: array -> arrays

section 2.3, line 2/3 after list: as descriptor -> as a descriptor

section 3, para 6, line 9: 32 bits -> 32 bit

section 3, para 6, last sentence -> A malicious program might in this way
access every object in the system.

section 4, para 1, line 1: made experimental -> made an experimental

section 4, para 4: check -> checks
                   if argument's -> if the argument's
                   effect for -> effect of

section 4, para 5, line 1: still subset -> still a subset

section 5, para 1, line 2: compiles every Scheme -> compiles Scheme

section 5, para 2, line 4: 31 bit -> 31 bits

section 6.2, heading: arithmetics -> arithmetic

section 6.2, para 2, line 3:  then -> than

section 6.3 "No perfromance penalties are observed" - you should explicitly
mention that performance gains are observed.

section 7, para 1, line 6: introduces -> introduce

section 7, para 3, line 4: has same problem -> has the same problems

section 7, para 3, line 11: more generic -> a more generic

Comments to referee:

This seems fine, but I am not very familiar with this area.