harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Varlamov" <alexey.v.varla...@gmail.com>
Subject Re: [drlvm] Cleaning insides of Class.h header
Date Tue, 05 Sep 2006 11:10:53 GMT
+1 for cleanup, I could even assist you.
Please also consider possible dependency on issue #1363.

--
Regards,
Alexey

2006/9/5, Pavel Pervov <pmcfirst@gmail.com>:
> It's been long time this discussion stopped.
> This may mean three things:
> - first, everyone agrees this should be done and I'm ok to provide
> consecutive patches;
> - second, noone clearly understand the purpose of what is suggested to do;
> if this is the case, do not hesitate to ask (again?);
> - third, noone is really interested in making source code of DRLVM more
> readable and more understandable, and I should drop this activity.
>
> Meanwhile, I'd like to open jira and start posting patches there.
>
> Regards,
>    Pavel.
>
> On 7/25/06, Pavel Pervov <pmcfirst@gmail.com> wrote:
> >
> >  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 <geir@pobox.com> wrote:
> > >
> > >
> > >
> > > Pavel Pervov wrote:
> > > > On 7/24/06, Alexey Petrenko < alexey.a.petrenko@gmail.com> wrote:
> > > >>
> > > >> 2006/7/24, Pavel Pervov <pmcfirst@gmail.com>:
> > >
> > > >> > 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: harmony-dev-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: harmony-dev-help@incubator.apache.org
> > >
> > >
> >
>
>

---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org


Mime
View raw message