harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Pervov (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-1558) Cleaning insides of Class.h header
Date Sat, 23 Sep 2006 14:15:25 GMT
     [ http://issues.apache.org/jira/browse/HARMONY-1558?page=all ]

Pavel Pervov updated HARMONY-1558:

    Attachment: splitting-class-h.patch

The attached patch implements step 1 of proposed plan.

> Cleaning insides of Class.h header
> ----------------------------------
>                 Key: HARMONY-1558
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1558
>             Project: Harmony
>          Issue Type: Improvement
>          Components: DRLVM
>            Reporter: Pavel Pervov
>         Attachments: splitting-class-h.patch
> "I would like to work on cleaning the insides of Class.h header file.
> This header is related to internal representation of java class inside the VM. Currently
it contains all entities for internal class representation: class itself, constant pool, members
(field, method), exceptions handler, vtable and so forth. 
> First thing I would like to do is to split the file into a group of files, each of which
would contain only one entity (and some closely related entities, if any). This would produce
the following headers: 
> 1)       Class.h - constant pool and class
> 2)       vtable.h - vtable
> 3)       class_member.h - field and method entities descriptors, exception handler descriptor
> 4)       cci.h - code chunk entity (part of compiled method code)
> Second thing to do is to throw away members (and other stuff), which are not used anymore
and the only reason they are still there is history or they do not belong to these files.
> Third thing to do is to make all these entities C++ objects. Currently, member variables
of all listed entities are used arbitrarily throughout DRLVM code. I would like to regularize
usage and, also, document internals of these entities."

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message