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
API != ABI | 393 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
API != ABI
Authored by: Ian Al on Monday, May 28 2012 @ 03:49 AM EDT
I've been thinking about 'conceptual contract'.

I ended up with the shock realisation that the Java SE API is not an API. The
written contract is that if the many libraries are available to the compiler
then the compiler will execute the contract. If the named library code is not
present, then the compiler will not execute the contract.

The execution in the case of Java appears to me to be the copying of code into
the executable. In the case of Sony, it is a real API in that the contract says
that when certain instructions and parameters are 'passed across the interface'
then the receiving program will do certain things and respond with certain
data.

In the Sony case, it is both API and ABI because there are both implied
metaphors and contracts and there are simple exchanges of instructions and data
(ABIs are almost always bi-directional in that they will usually respond if the
instruction or data is invalid or if the receiving program has a partial
failure).

The most complex PI is the operating system interface. It is not intended just
for the highest level languages. Any API contracts, agreements or metaphors
exist even if assembly language is used to create a program that interfaces with
the operating system.

APIs have a richer capability of expressing the contract and the metaphors in an
understandable way using the language syntax. ABIs must have that richness
expressed in comments.

In both cases, the words in the specification/comments express the contract, but
in neither case is that contract apparent in the machine code. Because an API
has a richer contractual vocabulary in the language syntax, it has to have an
unwritten or written ABI in the path to using the interface.

---
Regards
Ian Al
Software Patents: It's the disclosed functions in the patent, stupid!

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