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
You're breaking it down a bit much | 141 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Absolutely correct
Authored by: argee on Friday, May 04 2012 @ 03:26 PM EDT
Your definition agrees with mine perfectly! But you said
it in 50 words, where my previous posting went to a lot
more. Perfect!

---
--
argee

[ Reply to This | Parent | # ]

I don't think that's fair..
Authored by: rcsteiner on Friday, May 04 2012 @ 04:13 PM EDT
Agreed. :-)

---
-Rich Steiner >>>---> Mableton, GA USA
The Theorem Theorem: If If, Then Then.

[ Reply to This | Parent | # ]

You're breaking it down a bit much
Authored by: Anonymous on Friday, May 04 2012 @ 04:24 PM EDT
You're trying to come up with an exhaustive list. In doing so, you've forgotten
about exceptions (sure, other languages don't have them, but Java _does_). And
yes, it is necessary to know which classes of exceptions (if any) a method
throws.

Also both input and output are optional. The RNG's seed function may take an
argument, but the function that gets a random number doesn't take any input at
all. It's even conceivable to have a function that has neither input NOR
output. Imagine a function that turns a device off, for example. Yeah, such
functions are pretty rare. Also, object types and their interfaces matter.

That's why I just say that the API encompasses all the rules which two programs
use to communicate with each other. The specifics of *what* is required for
communication depend on the language. Going into too many details just bogs us
down.

I mean, if you don't *have* exceptions in your language, they can't very well be
part of an API. But in Java? They are. The API is abstract, trying to boil it
down to a language-dependent checklist is, IMHO, more confusing than necessary.

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