guys a stupid question.....
what does API stands 4?????
plz reply asap
thanks
what does API stands 4?????
plz reply asap
thanks
-
-
Re: API
Application Program(ming) Interface.
A great source for this kind of questions
I hope this helps,
Cor
-
Re: API
<mohit.akl@gmai l.com> schrieb:[color=blue]
> what does API stands 4?????[/color]
"Applicatio n Programming Interface". Often API is used as synonym for the
Win32 API and 'Declare'/'DllImport' stuff, but in general even the .NET
Framework is an API.
--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>
Comment
-
Re: API
Herfried,
[color=blue]
> but in general even the .NET Framework is an API.[/color]
As the .Net Framework is a layer from the OS than it cannot be an interface
to that.
In see definitly the .Net Framework as a layer from the OS.
Cor
Comment
-
Re: API
"Cor Ligthert [MVP]" <notmyfirstname @planet.nl> schrieb:[color=blue][color=green]
>> but in general even the .NET Framework is an API.[/color]
>
> As the .Net Framework is a layer from the OS than it cannot be an
> interface to that.
>
> In see definitly the .Net Framework as a layer from the OS.[/color]
This doesn't mean it's not an API. API simply means "interface used to
program an application". Check out the Wikipedia article in your post :-).
--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>
Comment
-
Re: API
Herfried K. Wagner [MVP] wrote:
[color=blue]
> "Cor Ligthert [MVP]" <notmyfirstname @planet.nl> schrieb:[color=green][color=darkred]
> >> but in general even the .NET Framework is an API.[/color]
> >
> > As the .Net Framework is a layer from the OS than it cannot be an
> > interface to that.
> >
> > In see definitly the .Net Framework as a layer from the OS.[/color]
>
> This doesn't mean it's not an API. API simply means "interface used to
> program an application". Check out the Wikipedia article in your post :-).
>
> --
> M S Herfried K. Wagner
> M V P <URL:http://dotnet.mvps.org/>
> V B <URL:http://classicvb.org/petition/>[/color]
Cor just loves to tease... ;-)
But seriously, I would tend to agree with Cor that the .NET Framework
does not fall into *generally* accepted meaning of the word API. I
would distinguish the terms "framework" and "API". What are your
thoughts on this ?
Comment
-
Re: API
"Cerebrus" <zorg007@sify.c om> schrieb:[color=blue][color=green][color=darkred]
>> >> but in general even the .NET Framework is an API.
>> >
>> > As the .Net Framework is a layer from the OS than it cannot be an
>> > interface to that.
>> >
>> > In see definitly the .Net Framework as a layer from the OS.[/color]
>>
>> This doesn't mean it's not an API. API simply means "interface used to
>> program an application". Check out the Wikipedia article in your post
>> :-).[/color]
>
> Cor just loves to tease... ;-)
>
> But seriously, I would tend to agree with Cor that the .NET Framework
> does not fall into *generally* accepted meaning of the word API. I
> would distinguish the terms "framework" and "API". What are your
> thoughts on this ?[/color]
Framework simply means a set of libraries, tools, etc. which can be used to
develop applications, for example. API is more about what we get (an
interface to parts of a system, application, library, whatever) to develop
applications against, in other words, it's basically a contract). So, while
the .NET Framework is a framework that includes libraries (which define an
API), development and configuration tools, etc., the .NET Framework's class
library provides an API.
--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>
Comment
-
Re: API
Herfried,
[color=blue]
> Framework simply means a set of libraries, tools, etc. which can be used
> to develop applications, for example.[/color]
I would not say it like that, it is a part of the OS where against the CLI
code can run.
In my opinion is it the same is for every layer from an OS. That does not
make them an API.
The CLI code contains interfaces to that part of the OS but that does not
make it an API.
If you tell that inside this definition the classes distributed by the
development part of the framework are API's than I am in more trouble to
deny what you wrote. However that makes from every application itself almost
an API. In my opinion is an API more restricted to one function from the OS.
But just my thought,
Cor
"Herfried K. Wagner [MVP]" <hirf-spam-me-here@gmx.at> schreef in bericht
news:ux3SyKjiGH A.4896@TK2MSFTN GP05.phx.gbl...[color=blue]
> "Cerebrus" <zorg007@sify.c om> schrieb:[color=green][color=darkred]
>>> >> but in general even the .NET Framework is an API.
>>> >
>>> > As the .Net Framework is a layer from the OS than it cannot be an
>>> > interface to that.
>>> >
>>> > In see definitly the .Net Framework as a layer from the OS.
>>>
>>> This doesn't mean it's not an API. API simply means "interface used to
>>> program an application". Check out the Wikipedia article in your post
>>> :-).[/color]
>>
>> Cor just loves to tease... ;-)
>>
>> But seriously, I would tend to agree with Cor that the .NET Framework
>> does not fall into *generally* accepted meaning of the word API. I
>> would distinguish the terms "framework" and "API". What are your
>> thoughts on this ?[/color]
>
> Framework simply means a set of libraries, tools, etc. which can be used
> to develop applications, for example. API is more about what we get (an
> interface to parts of a system, application, library, whatever) to develop
> applications against, in other words, it's basically a contract). So,
> while the .NET Framework is a framework that includes libraries (which
> define an API), development and configuration tools, etc., the .NET
> Framework's class library provides an API.
>
> --
> M S Herfried K. Wagner
> M V P <URL:http://dotnet.mvps.org/>
> V B <URL:http://classicvb.org/petition/>[/color]
Comment
-
Re: API
"Cor Ligthert [MVP]" <notmyfirstname @planet.nl> schrieb:[color=blue][color=green]
>> Framework simply means a set of libraries, tools, etc. which can be used
>> to develop applications, for example.[/color]
>
> I would not say it like that, it is a part of the OS where against the CLI
> code can run.[/color]
The .NET Framework is not part of the OS. It's simply a layer that is built
on top of the OS core functionality.
[color=blue]
> In my opinion is it the same is for every layer from an OS. That does not
> make them an API.[/color]
It doesn't, but each layer can expose an API! Otherwise it would be
impossible to develop drivers, normal applications, etc. for Windows.
[color=blue]
> The CLI code contains interfaces to that part of the OS but that does not
> make it an API.[/color]
I am not sure what exactly you are referring to with CLI (typically this
stands for "Common Language Infrastructure" ).
[color=blue]
> If you tell that inside this definition the classes distributed by the
> development part of the framework are API's[/color]
No, I do not claim that. As I mentioned before, I see APIs as something
more abstract. A library is not the same as an API. An API consists of one
or more libraries which export functions, classes, etc., and are documented
and maybe specified, for example.
[color=blue]
> However that makes from every application itself almost an API.[/color]
Not really. An application typically does not expose interfaces which can
be used by other developers to develop applications which inteact with the
application. However, there are some applications such as Word and Excel
which expose automation and extensibility functionality through APIs.
[color=blue]
> In my opinion is an API more restricted to one function from the OS.[/color]
?!?
--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>
Comment
-
Re: API
mohit.akl@gmail .com wrote:
[color=blue]
>guys a stupid question.....
>what does API stands 4?????
>plz reply asap
>thanks
>
>
>[/color]
These two guys are so funny - API = Application Programming Interface.
It tells the whole story. It is an interface that can be used in the
programming of an application. It doesn't say anywhere that it has to
be made available by the OS. So, the OS, a component, a custom dll, all
can provide an API.
If your application is using the interface provided by some other code,
in your programming, then that is and API. Code is code. OS is just
code. Why get so caught up in insignificant details of where that code
resides?
Tom
Comment
-
Re: API
Herfried,
I stop this with exception from one.
[color=blue]
> I am not sure what exactly you are referring to with CLI (typically this
> stands for "Common Language Infrastructure" ).
>[/color]
For me this stands typically for "Cor Ligthert" (as often used abrivation).
:-)
Cor
Comment
-
Re: API
Tomb,
[color=blue][color=green]
>>[/color]
> These two guys are so funny - API = Application Programming Interface.[/color]
We both told that in our first reply, where I gave a link Wikepedi which
explains it very good.
However there is nothing wrong as in a board something becomes a more
theoretical discussion.
That is where Usenet (NNTP) was build for.
Cor
Comment
-
Re: API
tomb wrote:
[color=blue]
> These two guys are so funny - API = Application Programming Interface.
> It tells the whole story. It is an interface that can be used in the
> programming of an application. It doesn't say anywhere that it has to
> be made available by the OS. So, the OS, a component, a custom dll, all
> can provide an API.
>
> If your application is using the interface provided by some other code,
> in your programming, then that is and API. Code is code. OS is just
> code. Why get so caught up in insignificant details of where that code
> resides?
>
> Tom[/color]
Rather simplifying it, aren't you ! I think both of our veteran
specialists (I refrain from using the word "guys") have made such valid
points that I'm now confused. But not that it matters much.
Comment
Comment