©1996-2012 Roedy Green, Canadian Mind ProductsThis essay does not describe an existing computer program, just one that should exist. This essay is about a suggested student project in Java programming. This essay gives a rough overview of how it might work. I have no source, object, specifications, file layouts or anything else useful to implementing this project.
This project outline is not like the artificial, tidy little problems you are spoon-fed in school, when all the facts you need are included, nothing extraneous is mentioned, the answer is fully specified, along with hints to nudge you toward a single expected canonical solution. This project is much more like the real world of messy problems where it is up to you to fully the define the end point, or a series of ever more difficult versions of this project, and research the information yourself to solve them.
Everything I have to say to help you with this project is written below. I am not prepared to help you implement it; or give you any additional materials. I have too many other projects of my own.
Though I am a programmer, I don’t do people’s homework for them. That just robs them of an education.
You have my full permission to implement this project in any way you please and to keep all the profits from your endeavour.
Please do not email me about this project without reading the disclaimer above.
If you have a Java version 1.3 installed, how can you check if the code will run on JDK (Java Development Kit) 1.1 or 1.2? You would have to install the older JDK, recompile and test. Would it not be convenient if you could just run a utility that gave a you a list of classes that you used that were not available in the older JDK. The list would tell you, " If you could avoid using these classes/methods, this code would work under version 1.1 "How would you prepare the tables of methods available in each JDK? You would use reflection to wander through all the system jars to collect a list of classes and methods. You would need to create one such list for each JDK. You would use a similar technique to find all the user’s classes.
How would you find out what classes and methods the application uses? You have to partially disassemble the class file headers. See JASM and disassembler.
You also might modify the doclet that generates the Javadoc to ghost the entries you can’t use for a given project.
In the meantime, to prepare code for an older version of Java use:
Alternatively, keep a stable of old complete JDK ’s about and compile and test in the oldest one you want to still support your code.
 |
You can get the freshest copy of this page from: | or possibly from your local J: drive (Java virtual drive/mindprod.com website mirror) |
| http://mindprod.com/project/jdkversion.html | J:\mindprod\project\jdkversion.html | |
 | Please email your feedback for publication,
letters to the editor, errors, omissions, typos, formatting errors, ambiguities, unclear wording,
broken/redirected link reports, suggestions to improve this page or comments to
Roedy Green :
 .
If you want your message, your name or email kept confidential, not considered for public posting, please explicitly specify that.
Unless you state otherwise, I will treat your message as a letter to the editor that I may or may not publish in the feedback section. After that, it will be too late to retract it.
If you disagree with something I said, please quote it and cite the web page where you found it, tell me why you think it is wrong,
and, if possible, provide some supporting evidence. Threatening to kill me or spouting obscenities has yet to persuade me to change my mind. | |
| Canadian Mind Products | ||
| mindprod.com IP:[65.110.21.43] | ||
| view Blog | Your face IP:[38.107.179.214] | |
| Feedback | You are visitor number 7,065. | |
