Differences between current version and revision by previous author of ClassFile.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 3 | Last edited on Friday, September 12, 2003 2:44:51 pm | by DavidHallett | |
| Older page: | version 1 | Last edited on Monday, August 25, 2003 11:35:04 am | by StuartYeates | Revert |
@@ -1,5 +1,5 @@
-[ClassFile]s are the ByteCode form of [Java]. They are platform independant and one of the mani
reasons for the success of the Java language. They are normally distributed in JarFile, which is a specialisation of a [zip(1)] file.
+[ClassFile]s are the ByteCode form of [Java]. They are platform independant and one of the main
reasons for the success of the Java language. They are normally distributed in JarFile, which is a specialisation of a [zip(1)] file.
The ClassFile is built around a Constant Pool, which is rather like a symbol table in a [Fortran] library.
A Number of key limitations are introduced into Java systems by the [ClassFile] format, including:
@@ -9,5 +9,5 @@
# The number of fields that may be declared by a class or interface is limited to 65535
# The number of methods that may be declared by a class or interface is limited to 65535
# The number of direct superinterfaces of a class or interface is limited to 65535
-These issues are not usually a problem for hand-written code, but [CompilerCompiler]s often generate finite state machines which run into these. The cannonical
reference for these issues is: [http://java.sun.com/docs/books/vmspec/2nd-edition/html/ClassFile.doc.html]
+These issues are not usually a problem for hand-written code, but [CompilerCompiler]s often generate finite state machines which run into these. The canonical
reference for these issues is: [http://java.sun.com/docs/books/vmspec/2nd-edition/html/ClassFile.doc.html]
