Connecting Tech Pros Worldwide Forums | Help | Site Map

Still the confusion is there ....

Madni
Guest
 
Posts: n/a
#1: Dec 6 '06
hi,
can any one please let me know whats the clear and stratight difference
between the most commonly used terms "SDK", "API", and "Library" .....
Regards,
Omer


Jim Langston
Guest
 
Posts: n/a
#2: Dec 6 '06

re: Still the confusion is there ....


"Madni" <omermadni@gmail.comwrote in message
news:1165379626.176777.268350@j44g2000cwa.googlegr oups.com...
Quote:
hi,
can any one please let me know whats the clear and stratight difference
between the most commonly used terms "SDK", "API", and "Library" .....
Regards,
Omer
SDK is "Software Development Kit". This is just something you need to get
to be able to use something in code. For example, Microsoft provides an SDK
for DirectX, which includes headers, libraries, manuals, tutorials, etc...

API is "Advanced Programming Interface". Advanced may not be the right word.
An API is just an interfact to call something, usually in a library.
Windows has lots of calls you make to APIs.

A Library is precompiled code. There are different types of libraries, with
different terms used on different OSes. There are runtime libraries and
static link libraries. Basically they are precompiled code that you link
your program to.


Evan
Guest
 
Posts: n/a
#3: Dec 6 '06

re: Still the confusion is there ....



Jim Langston wrote:
Quote:
"Madni" <omermadni@gmail.comwrote in message
news:1165379626.176777.268350@j44g2000cwa.googlegr oups.com...
Quote:
hi,
can any one please let me know whats the clear and stratight difference
between the most commonly used terms "SDK", "API", and "Library" .....
Regards,
Omer
>
SDK is "Software Development Kit". This is just something you need to get
to be able to use something in code. For example, Microsoft provides an SDK
for DirectX, which includes headers, libraries, manuals, tutorials, etc...
>
API is "Advanced Programming Interface". Advanced may not be the right word.
An API is just an interfact to call something, usually in a library.
Windows has lots of calls you make to APIs.
*Application* programming interface.

I'll just add that I've heard sort of two uses of the word. (Two shades
of the same use might be a better description.) Sometimes you'll see it
used to refer to a collection of functions. For instance, the "Windows
API" is the set of C interfaces that MS defined to the Win32 subsystem.
There are also subsets of the Windows API that are referred to by other
names, like the File Management API. I've also heard it used to refer
to individual functions from said API, though this seems less common.
(In fact, that might have only been from MS.)

Evan

Quote:
>
A Library is precompiled code. There are different types of libraries, with
different terms used on different OSes. There are runtime libraries and
static link libraries. Basically they are precompiled code that you link
your program to.
Madni
Guest
 
Posts: n/a
#4: Dec 6 '06

re: Still the confusion is there ....



Thanks jim for taking out ur time and making the confusion clear....
Yes it is Application Programming Interface...
Regards

Jim Langston wrote:
Quote:
"Madni" <omermadni@gmail.comwrote in message
news:1165379626.176777.268350@j44g2000cwa.googlegr oups.com...
Quote:
hi,
can any one please let me know whats the clear and stratight difference
between the most commonly used terms "SDK", "API", and "Library" .....
Regards,
Omer
>
SDK is "Software Development Kit". This is just something you need to get
to be able to use something in code. For example, Microsoft provides an SDK
for DirectX, which includes headers, libraries, manuals, tutorials, etc...
>
API is "Advanced Programming Interface". Advanced may not be the right word.
An API is just an interfact to call something, usually in a library.
Windows has lots of calls you make to APIs.
>
A Library is precompiled code. There are different types of libraries, with
different terms used on different OSes. There are runtime libraries and
static link libraries. Basically they are precompiled code that you link
your program to.
supersizeme1234567890@yahoo.com
Guest
 
Posts: n/a
#5: Dec 6 '06

re: Still the confusion is there ....



Madni wrote:
Quote:
hi,
can any one please let me know whats the clear and stratight difference
between the most commonly used terms "SDK", "API", and "Library" .....
Regards,
Omer
I think API is shortened for Artificial Pig's Intelligence

Library is a Kamasutra of sex with each sections describing in details
how one should perform some specific tasks

I don't know about SDK :-( but I guess it might be something relating
to sexual diseases

Madni
Guest
 
Posts: n/a
#6: Dec 6 '06

re: Still the confusion is there ....


seams like been in a terrible programming experience .... :-P
supersizeme1234567890@yahoo.com wrote:
Quote:
Madni wrote:
Quote:
hi,
can any one please let me know whats the clear and stratight difference
between the most commonly used terms "SDK", "API", and "Library" .....
Regards,
Omer
>
I think API is shortened for Artificial Pig's Intelligence
>
Library is a Kamasutra of sex with each sections describing in details
how one should perform some specific tasks
>
I don't know about SDK :-( but I guess it might be something relating
to sexual diseases
benben
Guest
 
Posts: n/a
#7: Dec 6 '06

re: Still the confusion is there ....


I think API is shortened for Artificial Pig's Intelligence
Quote:
>
Library is a Kamasutra of sex with each sections describing in details
how one should perform some specific tasks
>
I don't know about SDK :-( but I guess it might be something relating
to sexual diseases
>
You may as well try to explain the namespace name for the standard C++
library.

Cough!

Ben
bogdan
Guest
 
Posts: n/a
#8: Dec 6 '06

re: Still the confusion is there ....



"""benben ΠΙΣΑΜ(Α):
"""
Quote:
Quote:
I think API is shortened for Artificial Pig's Intelligence

Library is a Kamasutra of sex with each sections describing in details
how one should perform some specific tasks

I don't know about SDK :-( but I guess it might be something relating
to sexual diseases
>
You may as well try to explain the namespace name for the standard C++
library.
>
Cough!
>
Ben
http://magegame.ru/?rf=626f6764616e

Marcus Kwok
Guest
 
Posts: n/a
#9: Dec 6 '06

re: Still the confusion is there ....


Jim Langston <tazmaster@rocketmail.comwrote:
Quote:
"Madni" <omermadni@gmail.comwrote in message
news:1165379626.176777.268350@j44g2000cwa.googlegr oups.com...
Quote:
>can any one please let me know whats the clear and stratight difference
>between the most commonly used terms "SDK", "API", and "Library" .....
>
API is "Advanced Programming Interface". Advanced may not be the right word.
Application Programming Interface is how I've usually heard it.
Quote:
A Library is precompiled code. There are different types of libraries, with
different terms used on different OSes. There are runtime libraries and
static link libraries. Basically they are precompiled code that you link
your program to.
I don't think a library necessarily needs to be precompiled. For
example, the Boost library comes in source/header form.

I would say that a library is a collection of related functions and/or
data types that are usually packaged together.

--
Marcus Kwok
Replace 'invalid' with 'net' to reply
Default User
Guest
 
Posts: n/a
#10: Dec 6 '06

re: Still the confusion is there ....


Madni wrote:
Quote:
>
Thanks jim for taking out ur time and making the confusion clear....

Please don't top-post. Your replies belong following or interspersed
with properly trimmed quotes. See the majority of other posts in the
newsgroup, or the group FAQ list:
<http://www.parashift.com/c++-faq-lite/how-to-post.html>
Old Wolf
Guest
 
Posts: n/a
#11: Dec 6 '06

re: Still the confusion is there ....


Default User wrote:
Quote:
Madni wrote:
Quote:
Thanks jim for taking out ur time and making the confusion clear....
>
Please don't top-post. Your replies belong following or interspersed
with properly trimmed quotes. See the majority of other posts in the
newsgroup, or the group FAQ list:
Top-posting was correct for that post. The message did not
relate to any particular part of the parent post, but was a
generalized comment on the whole thing. It was not
necessary to read the quotes in order to understand the
message.

Default User
Guest
 
Posts: n/a
#12: Dec 6 '06

re: Still the confusion is there ....


Old Wolf wrote:
Quote:
Default User wrote:
Quote:
Madni wrote:
Quote:
Thanks jim for taking out ur time and making the confusion
clear....
Please don't top-post. Your replies belong following or interspersed
with properly trimmed quotes. See the majority of other posts in the
newsgroup, or the group FAQ list:
>
Top-posting was correct for that post.
No, it wasn't.
Quote:
The message did not
relate to any particular part of the parent post, but was a
generalized comment on the whole thing.
Immaterial. If the entire content wasn't germane to the answer, it
should have been paraphrased or a small representative sample left to
give context.
Quote:
It was not
necessary to read the quotes in order to understand the
message.
Then why include all?



Brian
Old Wolf
Guest
 
Posts: n/a
#13: Dec 6 '06

re: Still the confusion is there ....


Default User wrote:
Quote:
Old Wolf wrote:
>
Quote:
The message did not
relate to any particular part of the parent post, but was a
generalized comment on the whole thing.
>
Immaterial. If the entire content wasn't germane to the answer, it
should have been paraphrased or a small representative sample left to
give context.
The entire content was suitable context.
Quote:
Quote:
It was not necessary to read the quotes in order to understand
the message.
>
Then why include all?
In case a reader is curious about what the message was replying
to, and doesn't have the original.

Default User
Guest
 
Posts: n/a
#14: Dec 6 '06

re: Still the confusion is there ....


Old Wolf wrote:
Quote:
Default User wrote:
Quote:
Old Wolf wrote:
Quote:
The message did not
relate to any particular part of the parent post, but was a
generalized comment on the whole thing.
Immaterial. If the entire content wasn't germane to the answer, it
should have been paraphrased or a small representative sample left
to give context.
>
The entire content was suitable context.
Nonsense. A small bit or a paraphrase would be much more appropriate.
You don't seriously expect people to read the entire quoted bit to
figure out what the reply meant, do you?
Quote:
Quote:
Quote:
It was not necessary to read the quotes in order to understand
the message.
Then why include all?
>
In case a reader is curious about what the message was replying
to, and doesn't have the original.
As I said, a small bit is more than adequate for a "thank you" message.




Brian
Closed Thread


Similar C / C++ bytes