Dissecting the class file format to see how a particular compiler translated your code can be a useful technique, but you can't depend on the output being the same when you use different compilers on different platforms
I can't understand why this(Dissecting the class file format) should be a problem.All classes must follow the java class file format (which is a Sun standard available at javasoft.com),so no matter which compiler you use the classes produced are in the same format(for example the magic number for a class file is "CAFEBABE" in Hex. If this were not so , diffrent jvm implementations would be unable to run the class files, thus , invalidating one of the design principles of Sun to make Java a write once run anywhere language.
Though the population of India is 1 billion, only
a miniscule percentage of it is educated,and of this miniscule group only a miniscule percentage is what I would call educated to western levels.
Slashdot Mirror
Of course, I can being an Indian Bengali and becuase I had English and French in School
Dissecting the class file format to see how a particular compiler translated your code can be a useful technique, but you can't depend on the output being the same when you use different compilers on different platforms I can't understand why this(Dissecting the class file format) should be a problem.All classes must follow the java class file format (which is a Sun standard available at javasoft.com),so no matter which compiler you use the classes produced are in the same format(for example the magic number for a class file is "CAFEBABE" in Hex. If this were not so , diffrent jvm implementations would be unable to run the class files, thus , invalidating one of the design principles of Sun to make Java a write once run anywhere language.
Though the population of India is 1 billion, only a miniscule percentage of it is educated ,and of this miniscule group only a miniscule percentage is what I would call educated to western levels.