|
Authored by: Anonymous on Friday, April 20 2012 @ 10:13 AM EDT |
java.nio.ByteBuffer, has a bunch of associated methods and fields, it would be
stupid and ridiculous, to creatively decide to move ByteBuffer methods to a
different class java.util.Array. The OOP paradigm is one of encapsulation.
Thus the Methods of the ByteBuffer class, are themselves members of the
ByteBuffer Class.
SSO can only occur at the package/class level, everything else is OOP
Encapsulation.
javax.security.auth.x500 could in theory be moved say.
java.util.x500, but this would be *bad* and would confuse a lot of people.
There is no correlation between java.io and java.util
There may be a slight correlation between the Classes of the java.io package,
but that is an extension of OOP encapsulation extended to Packages, to group
together functionality related Classes.
There is no correlation amongst the member Classes of java.util, Oracle
themselves called it a mixed bag while claiming with a straight face that this
dumping ground for utilities was somehow the consequence of countless years and
millions of dollars worth of creative design decision.
There is no correlation between the classes
[ Reply to This | Parent | # ]
|
|
|
|
|