Geir, well, it is the argument at least for me to start thinking in this direction and initiate this discussion.
And there are places in VM core code where only definition of members of a class is required, but whole Class.h is included anyway. This is also about localizing potential development in separate functional groups to reduce recompilation when working intensively with these files. Hope, I answered, what you were asking about. :) Regards, Pavel. On 7/24/06, Geir Magnusson Jr <[EMAIL PROTECTED]> wrote:
Pavel Pervov wrote: > On 7/24/06, Alexey Petrenko <[EMAIL PROTECTED]> wrote: >> >> 2006/7/24, Pavel Pervov <[EMAIL PROTECTED]>: >> > 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) >> >> Will these header files be useful separately? > > > Yes, sure, they will be. This is one of the arguments for doing so. > To whom? geir --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
