decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
OOP is causation not correlaton. | 270 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
OOP is causation not correlaton.
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 | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )