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
Grouping methods together | 52 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Grouping methods together
Authored by: mschmitz on Monday, April 23 2012 @ 04:26 PM EDT
The judge explicitly asks about inheritance here. From that point of view,
grouping related things together (here maths) is pretty much mandatory as long
as you wish to retain a reasonably coarse-grained API. The cosine function can
inherit types from the math class, and its implementation will likely derive
from common algorithms used for other trig functions.

Anything that is just implements maths can go in the same class. Anything that
just uses maths inherits from it (your XML class). If you want to prevent XML to
pull in cosine code, or put cosine in with another class, you'd have to put all
the types in a separate class. Only then would that hypothetical class _not_
depend on the math class because of the required types (and possibly private
methods for the algorithm). True Java heads please correct me if I'm wring
here.

(I don't think inheritance of some class from math just for the purpose of a
single function is much of a problem in practice, once the references have been
resolved and the bytecode is loaded. The question appears to be conceptual in
nature - the judge has come to the conclusion that certain groupings of
functions the way they are specified have to be done just so for a sound
technical reason, not 'creative expression', and is looking for confirmation.)

-- mschmitz

[ Reply to This | Parent | # ]

Oracle v. Google - More Weekend Filings - The Most Recent Briefs on Copyright Liability
Authored by: Oliver on Monday, April 23 2012 @ 04:35 PM EDT
The main efficiency of the "Correct" grouping is a reduction
in dependencies between packages. A tree structure is better
than a graph, i.e. all dependencies flow in one direction so
that there is one package that depends on no others.

[ 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 )