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
It's part alphabetical order, and part no order | 503 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Oracle must be concerned now
Authored by: ThrPilgrim on Saturday, April 21 2012 @ 05:23 PM EDT
what order should the methods appear in? It doesn't actually matter

Actually the order of the methods may well be more constrained than you think, as you will want to minimise forward declarations of functions in the package.

This assumes that you have to declare methods/functions in Java before you can use them. I don't know enougth about Java to know if this is true or not.

---
Beware of him who would deny you access to information for in his heart he considers himself your master.

[ Reply to This | Parent | # ]

It's part alphabetical order, and part no order
Authored by: bugstomper on Saturday, April 21 2012 @ 08:18 PM EDT
The Javadoc documentation that is generated from the source code with comments
sorts everything into alphabetical order for the summary sections, so you can
look things up easily. The full text descriptions of the methods appear in the
documentation in the order the methods appear in the source code implementation,
which is an arbitrary order that has no significance. There would be no reason
for someone doing a clean room implementation of a class to write the methods in
the same order as in Sun's JDK implementation of that class.

No matter what order the methods appear in the source code of class, the Javadoc
API documentation that is generated from it would have the identical method
signatures (except for the arbitrary argument names) listed in the identical
(alphabetical) order in the summary sections. The only thing that would be
different in those sections would be the brief English description of what the
method does. Later, in the full section, the methods would appear in different
arbitrary order, again the signatures being the same except possible for
argument names, and the English text descriptions being different.

I don't know what the ramifications would be if someone did copy the order that
public methods were defined in a class. Since the order provides no value and
expresses no idea of consequence, is it a copyrightable element of the
implementation code of the class?

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