Right. Order of parameters in a method signature does matter, and for
functional compatibility it MUST be exactly the same.
The order of methods
in a class (in the source code) doesn't matter. Javadoc-generated documentation
doesn't even list them in that order. It lists
them in ALPHABETICAL order! That's right, the Android documentation the
Oracle thinks was copied from Sun's documentation, lists these things in
alphabetical order.
"Order of classes in a package" doesn't matter, and I
would argue that it doesn't exist at all. The "classes in a package" are
separate files in a directory, and those are were not authored in a particular
order the way the methods of a single class are. File system directories are
just a grab-bag of files, which can be listed in any sorted order that the user
prefers. For the same reason, order of sub-packages within a parent package
doesn't exist. [ Reply to This | Parent | # ]
|