Please stop incrementing the classfile version number when there are no format changes (original) (raw)
Remi Forax forax at univ-mlv.fr
Fri Oct 11 19:39:43 UTC 2019
- Previous message: Please stop incrementing the classfile version number when there are no format changes
- Next message: Where is the streams API using ForkJoinPool?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
P.S. Mike your point about a bundled ASM is a very good one. The lack of a bytecode spinner in the JDK is long-standing tech. debt, on which the interest rate has risen (because the payments are the same but now come due every six months). Who’s on the hook to fix this? All of us, really; it’s the OpenJDK. Starting up a JEP would make a good place to gather information about options and requirements. — John
The problem of bundling it in the JDK is that it forces people that maintains libraries that want to read/write the newest classfiles to be compatible with the newest JDK unlike ASM which only requires Java 5. So it will solve the problem of Mike but will cause problems to others that have not yet migrated their libraries to the newest JDK.
Rémi
- Previous message: Please stop incrementing the classfile version number when there are no format changes
- Next message: Where is the streams API using ForkJoinPool?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]