Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of pmcfirst@gmail.com designates
 66.249.82.225 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=fBB2sJ/2J82X25kwwcar8n9LcigIAzWfSZ0DzU08SIZV1X4nZAF/cNkOvsPxg5/05o/5jNkouKG6PpTLPv/IS8cxiTok8/eOyZCCHgiYET11X465Q5SA30+FFtVym9TQsob81zdOUiyQbH96qM2cxdloEk5iIXR7v56zDqMBOK4=
Message-ID: <e0f125db0609050325v75420bb0i7b3cdb0bcbf087d8@mail.gmail.com>
Date: Tue, 5 Sep 2006 14:25:46 +0400
From: "Pavel Pervov" <pmcfirst@gmail.com>
To: harmony-dev@incubator.apache.org
Subject: Re: [drlvm] Cleaning insides of Class.h header
In-Reply-To: <e0f125db0607250208i26bcbd61h331410fc06f6ddc6@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_75480_2312750.1157451946376"
References: <e0f125db0607240324w15fba97bj3f1573826b3b27fb@mail.gmail.com>
	 <c3755b3a0607240337i26f10249i78cb9f29045b9f10@mail.gmail.com>
	 <e0f125db0607240402w28067574n28f7aab45f07e833@mail.gmail.com>
	 <44C4E656.4050101@pobox.com>
	 <e0f125db0607250208i26bcbd61h331410fc06f6ddc6@mail.gmail.com>

------=_Part_75480_2312750.1157451946376
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

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 o=
f
> >
> > >> 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 =96 constant pool and class
> > >> > 2)       vtable.h =96 vtable
> > >> > 3)       class_member.h =96 field and method entities descriptors,
> > >> exception
> > >> > handler descriptor
> > >> > 4)       cci.h =96 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
> >
> >
>

------=_Part_75480_2312750.1157451946376--