> >is there a tool to check specified sourcecode for the JVM it need at
> >minimum to run properly?
>
> You can try compiling it on a variety of JVMS, or with a variety of
> bootclass libraries and see what works and what does not.
mhh.. i was looking for something more automated ;) I think it would
be really useful. You might want to check for v1.2 compatability for
example, to know if the javacode will compile with gcj.
> Perhaps you could prepare a list of all the classes you use, and
> extract the SINCE commands from the source or Javadoc. Fill in any
> missing ones.
> The tool could be very useful generally. However, even then you are
> not safe, since some classes added methods, or deprecated methods.
> you really need to do it on a method level.
I thought of the SINCE tag.. but since methods are not tagged with it
it won't be worth anything.
> You could exract the files from classes.zip/rt.jar for each old JVM,
> and produce a list of class/method/signatures. Then extract the same
> from your class files. See http://mindprod.com/jgloss/jasm.html
> for how.
good idea.. if I had the time I'd do it but such a tool is not that
important
for me. I was just wondering whether something like that exists
already..
> Sounds like time to write up yet another student project.
yep.. I'll recommend that at my university at once!
Roedy Green - 07 May 2004 20:48 GMT
>I thought of the SINCE tag.. but since methods are not tagged with it
>it won't be worth anything.
Can they be? I suppose you could infer the since tag from the since
on the class, or from something you provide manually from your own
knowledge.
--
Canadian Mind Products, Roedy Green.
Coaching, problem solving, economical contract programming.
See http://mindprod.com/jgloss/jgloss.html for The Java Glossary.
brian - 10 May 2004 15:57 GMT
> >I thought of the SINCE tag.. but since methods are not tagged with it
> >it won't be worth anything.
>
> Can they be? I suppose you could infer the since tag from the since
> on the class, or from something you provide manually from your own
> knowledge.
Unfortunately not. Classes in JDK 1.4.2 are tagged with 1.1 but offer
methods which weren't there in 1.1. I think the easiest thing to do
would be setting up a database (for quick search) with all classes and
method signatures and tag the signatures with the earliest version
where it was found.
It DOES sound like a good student project ;)
cheers
brian
Roedy Green - 10 May 2004 23:11 GMT
On 10 May 2004 07:57:25 -0700, daxel3@gmx.net (brian) wrote or quoted
>It DOES sound like a good student project ;)
It has been for a long time, though the outline of how to implement is
brief.
http://mindprod.com/projjdkversion.html
--
Canadian Mind Products, Roedy Green.
Coaching, problem solving, economical contract programming.
See http://mindprod.com/jgloss/jgloss.html for The Java Glossary.