|
Authored by: alisonken1 on Friday, May 31 2013 @ 11:30 AM EDT |
Based on the last statement in 2) it appears you don't know
or fail to understand what an Application Programming
Interface is.
In your example, Compaq created their own API for their BIOS
- but lo and behold, it matched enough of IBM's API that
_other programs_ written for the IBM BIOS could actually use
the same calls without needing interpretation.
Interesting concept that you think there's no API in use
there.
---
- Ken -
import std_disclaimer.py
Registered John Doe^W^WLinux user #296561
Slackin' since 1993
http://www.slackware.com[ Reply to This | Parent | # ]
|
- no .... - Authored by: Anonymous on Friday, May 31 2013 @ 11:49 AM EDT
|
Authored by: Anonymous on Friday, May 31 2013 @ 12:01 PM EDT |
An API is simply a kind of protocol.
Every protocol is, of course, conceptual--that is, it defines a
"language", a context in which "communication" of
"information" can occur.
You cannot divide the universe of thoughts up into "languages",
"APIs", "ABIs", "instruction sets", and
"protocols", and treat each one differently. They are all the same
thing. "If you want to communicate this datum, here's how you do it."
[ Reply to This | Parent | # ]
|
|
|
|
|