sablevm-developer

[Sablevm-developer] reflection update

[David P. B. <db...@CS...>]

Hello,

I have implemented:
- several reflection methods
- a basic Runtime.exec()
- ProcessImpl that implements Process's abstract methods.

I have fixed some bugs in some reflection functions that were already
implemented.

I was able to run:
- jUnit that uses getMethods()
- ant that uses getMethods() and that fork/exec to run Jikes

I am currently checking/cleaning up code.  Patches could be made
available tomorrow or the day after.  The code is still *very*
experimental.

Etienne,
I would like to know what would be the best way to make these changes
available.  Send a big patch to this list, put it on the web, wait for a
development branch,...  Note that the new code is still under
development and may change frequently.


David

---

David B=E9langer
Graduate Student
School of Computer Science
McGill University
Office: MC226

Web page:   http://www.cs.mcgill.ca/~dbelan2/
Public key: http://www.cs.mcgill.ca/~dbelan2/public_key.txt

Re: [Sablevm-developer] reflection update

[Grzegorz B. P. <ga...@de...>]

W li=B6cie z nie, 09-02-2003, godz. 08:36, David Paul BELANGER pisze:=20
> Hello,
>=20
> I have implemented:
> - several reflection methods
> - a basic Runtime.exec()
> - ProcessImpl that implements Process's abstract methods.
>=20
> I have fixed some bugs in some reflection functions that were already
> implemented.
>=20
> I was able to run:
> - jUnit that uses getMethods()
> - ant that uses getMethods() and that fork/exec to run Jikes
Terrific!
I was about to ask for the status.

> I am currently checking/cleaning up code.  Patches could be made
> available tomorrow or the day after.  The code is still *very*
> experimental.
I don't know how being experimental affects normal usage in this
case (stability, bugs etc.) but if it makes it possible to run
ANT with SableVM - I think we need it.

> Etienne,
> I would like to know what would be the best way to make these changes
> available.  Send a big patch to this list, put it on the web, wait for a
> development branch,...  Note that the new code is still under
> development and may change frequently.
We don't have sablevm-patches (and I am not sure that such list is
really needed now) so I'd propose:
1. If the diff isn't too big (say 20-40kb max) - you can attach it
to a mail to devel list
2. You can always put it somewhere on the web and give URL to it.
If the diff is subject to frequent changes - it can be good idea to
have date in the filename and (in the future) against what official
release it was created (or CVS date if you work on CVS version).

If the code is usable (it really runs ANT) - I'd like to see new
official release, maybe even this week, even if ANT support would be
marked "experimental".

Thank you for your work David

					Grzegorz B. Prokopski
--=20
Grzegorz B. Prokopski <ga...@de...>
Debian http://www.debian.org/

Re: [Sablevm-developer] reflection update

[David P. B. <db...@CS...>]

On Sun, Feb 09, 2003 at 12:50:15PM +0100, Grzegorz B. Prokopski wrote:
> W li?cie z nie, 09-02-2003, godz. 08:36, David Paul BELANGER pisze:=20
> > Hello,
> >=20
> > I have implemented:
> > - several reflection methods
> > - a basic Runtime.exec()
> > - ProcessImpl that implements Process's abstract methods.
> >=20
> > I have fixed some bugs in some reflection functions that were already
> > implemented.
> >=20
> > I was able to run:
> > - jUnit that uses getMethods()
> > - ant that uses getMethods() and that fork/exec to run Jikes
> Terrific!
> I was about to ask for the status.
>=20
> > I am currently checking/cleaning up code.  Patches could be made
> > available tomorrow or the day after.  The code is still *very*
> > experimental.
> I don't know how being experimental affects normal usage in this
> case (stability, bugs etc.) but if it makes it possible to run
> ANT with SableVM - I think we need it.

My goal was to get a quick working system that runs jUnit and ant.  It
is experimental in the sense that some new functionality is partially
implemented, not fully tested.  There may still be debugging code etc.
However, it should not affect the other parts of SableVM.

>=20
> > Etienne,
> > I would like to know what would be the best way to make these changes
> > available.  Send a big patch to this list, put it on the web, wait fo=
r a
> > development branch,...  Note that the new code is still under
> > development and may change frequently.
> We don't have sablevm-patches (and I am not sure that such list is
> really needed now) so I'd propose:
> 1. If the diff isn't too big (say 20-40kb max) - you can attach it
> to a mail to devel list
> 2. You can always put it somewhere on the web and give URL to it.
> If the diff is subject to frequent changes - it can be good idea to
> have date in the filename and (in the future) against what official
> release it was created (or CVS date if you work on CVS version).

The patch is posted on this web page, right at the end:
http://www.sable.mcgill.ca/~dbelan2/sablevm/hacking.html
(the patch is over 70k)

There is also a status file that says which functions have been
implemented.

Also, some functionality has been implemented in java instead of C.


> If the code is usable (it really runs ANT) - I'd like to see new
> official release, maybe even this week, even if ANT support would be
> marked "experimental".

I tested it with ant only on a small build file.  Ant users, let me know
if you run into problems.

I have been using it for some time with jUnit (that uses getMethods())
without problems.



Have fun!


David

---

David B=E9langer
Graduate Student
School of Computer Science
McGill University
Office: MC226

Web page:   http://www.cs.mcgill.ca/~dbelan2/
Public key: http://www.cs.mcgill.ca/~dbelan2/public_key.txt

Re: [Sablevm-developer] reflection update

[David P. B. <db...@CS...>]

Sorry, the patch will not work as it does not include the new files.  I
will try it again, test it on CVS and post an updated version ASAP on
the web site.

David

On Sun, Feb 09, 2003 at 10:57:43PM -0500, David Paul BELANGER wrote:
> On Sun, Feb 09, 2003 at 12:50:15PM +0100, Grzegorz B. Prokopski wrote:
> > W li?cie z nie, 09-02-2003, godz. 08:36, David Paul BELANGER pisze:=20
> > > Hello,
> > >=20
> > > I have implemented:
> > > - several reflection methods
> > > - a basic Runtime.exec()
> > > - ProcessImpl that implements Process's abstract methods.
> > >=20
> > > I have fixed some bugs in some reflection functions that were alrea=
dy
> > > implemented.
> > >=20
> > > I was able to run:
> > > - jUnit that uses getMethods()
> > > - ant that uses getMethods() and that fork/exec to run Jikes
> > Terrific!
> > I was about to ask for the status.
> >=20
> > > I am currently checking/cleaning up code.  Patches could be made
> > > available tomorrow or the day after.  The code is still *very*
> > > experimental.
> > I don't know how being experimental affects normal usage in this
> > case (stability, bugs etc.) but if it makes it possible to run
> > ANT with SableVM - I think we need it.
>=20
> My goal was to get a quick working system that runs jUnit and ant.  It
> is experimental in the sense that some new functionality is partially
> implemented, not fully tested.  There may still be debugging code etc.
> However, it should not affect the other parts of SableVM.
>=20
> >=20
> > > Etienne,
> > > I would like to know what would be the best way to make these chang=
es
> > > available.  Send a big patch to this list, put it on the web, wait =
for a
> > > development branch,...  Note that the new code is still under
> > > development and may change frequently.
> > We don't have sablevm-patches (and I am not sure that such list is
> > really needed now) so I'd propose:
> > 1. If the diff isn't too big (say 20-40kb max) - you can attach it
> > to a mail to devel list
> > 2. You can always put it somewhere on the web and give URL to it.
> > If the diff is subject to frequent changes - it can be good idea to
> > have date in the filename and (in the future) against what official
> > release it was created (or CVS date if you work on CVS version).
>=20
> The patch is posted on this web page, right at the end:
> http://www.sable.mcgill.ca/~dbelan2/sablevm/hacking.html
> (the patch is over 70k)
>=20
> There is also a status file that says which functions have been
> implemented.
>=20
> Also, some functionality has been implemented in java instead of C.
>=20
>=20
> > If the code is usable (it really runs ANT) - I'd like to see new
> > official release, maybe even this week, even if ANT support would be
> > marked "experimental".
>=20
> I tested it with ant only on a small build file.  Ant users, let me kno=
w
> if you run into problems.
>=20
> I have been using it for some time with jUnit (that uses getMethods())
> without problems.
>=20
>=20
>=20
> Have fun!
>=20
>=20
> David
>=20
> ---
>=20
> David B=E9langer
> Graduate Student
> School of Computer Science
> McGill University
> Office: MC226
>=20
> Web page:   http://www.cs.mcgill.ca/~dbelan2/
> Public key: http://www.cs.mcgill.ca/~dbelan2/public_key.txt

--=20

---

David B=E9langer
Graduate Student
School of Computer Science
McGill University
Office: MC226

Web page:   http://www.cs.mcgill.ca/~dbelan2/
Public key: http://www.cs.mcgill.ca/~dbelan2/public_key.txt

Re: [Sablevm-developer] reflection update

[David P. B. <db...@CS...>]

Ok it has been fixed.

I tested the patch on Debian GNU/Linux (both x86 and ppc) against a
clean CVS checkout.
(Note that the patch also includes my ppc patch since I didn't
unpatch it.  It shouldn't affect other architecture.)


David

On Mon, Feb 10, 2003 at 11:37:58AM -0500, David Paul BELANGER wrote:
>=20
> Sorry, the patch will not work as it does not include the new files.  I
> will try it again, test it on CVS and post an updated version ASAP on
> the web site.
>=20
> David
>=20
> On Sun, Feb 09, 2003 at 10:57:43PM -0500, David Paul BELANGER wrote:
> > On Sun, Feb 09, 2003 at 12:50:15PM +0100, Grzegorz B. Prokopski wrote=
:
> > > W li?cie z nie, 09-02-2003, godz. 08:36, David Paul BELANGER pisze:=
=20
> > > > Hello,
> > > >=20
> > > > I have implemented:
> > > > - several reflection methods
> > > > - a basic Runtime.exec()
> > > > - ProcessImpl that implements Process's abstract methods.
> > > >=20
> > > > I have fixed some bugs in some reflection functions that were alr=
eady
> > > > implemented.
> > > >=20
> > > > I was able to run:
> > > > - jUnit that uses getMethods()
> > > > - ant that uses getMethods() and that fork/exec to run Jikes
> > > Terrific!
> > > I was about to ask for the status.
> > >=20
> > > > I am currently checking/cleaning up code.  Patches could be made
> > > > available tomorrow or the day after.  The code is still *very*
> > > > experimental.
> > > I don't know how being experimental affects normal usage in this
> > > case (stability, bugs etc.) but if it makes it possible to run
> > > ANT with SableVM - I think we need it.
> >=20
> > My goal was to get a quick working system that runs jUnit and ant.  I=
t
> > is experimental in the sense that some new functionality is partially
> > implemented, not fully tested.  There may still be debugging code etc=
.
> > However, it should not affect the other parts of SableVM.
> >=20
> > >=20
> > > > Etienne,
> > > > I would like to know what would be the best way to make these cha=
nges
> > > > available.  Send a big patch to this list, put it on the web, wai=
t for a
> > > > development branch,...  Note that the new code is still under
> > > > development and may change frequently.
> > > We don't have sablevm-patches (and I am not sure that such list is
> > > really needed now) so I'd propose:
> > > 1. If the diff isn't too big (say 20-40kb max) - you can attach it
> > > to a mail to devel list
> > > 2. You can always put it somewhere on the web and give URL to it.
> > > If the diff is subject to frequent changes - it can be good idea to
> > > have date in the filename and (in the future) against what official
> > > release it was created (or CVS date if you work on CVS version).
> >=20
> > The patch is posted on this web page, right at the end:
> > http://www.sable.mcgill.ca/~dbelan2/sablevm/hacking.html
> > (the patch is over 70k)
> >=20
> > There is also a status file that says which functions have been
> > implemented.
> >=20
> > Also, some functionality has been implemented in java instead of C.
> >=20
> >=20
> > > If the code is usable (it really runs ANT) - I'd like to see new
> > > official release, maybe even this week, even if ANT support would b=
e
> > > marked "experimental".
> >=20
> > I tested it with ant only on a small build file.  Ant users, let me k=
now
> > if you run into problems.
> >=20
> > I have been using it for some time with jUnit (that uses getMethods()=
)
> > without problems.
> >=20
> >=20
> >=20
> > Have fun!
> >=20
> >=20
> > David
> >=20
> > ---
> >=20
> > David B=E9langer
> > Graduate Student
> > School of Computer Science
> > McGill University
> > Office: MC226
> >=20
> > Web page:   http://www.cs.mcgill.ca/~dbelan2/
> > Public key: http://www.cs.mcgill.ca/~dbelan2/public_key.txt
>=20
> --=20
>=20
> ---
>=20
> David B=E9langer
> Graduate Student
> School of Computer Science
> McGill University
> Office: MC226
>=20
> Web page:   http://www.cs.mcgill.ca/~dbelan2/
> Public key: http://www.cs.mcgill.ca/~dbelan2/public_key.txt

--=20

---

David B=E9langer
Graduate Student
School of Computer Science
McGill University
Office: MC226

Web page:   http://www.cs.mcgill.ca/~dbelan2/
Public key: http://www.cs.mcgill.ca/~dbelan2/public_key.txt