|
web
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
|
guys a stupid question.....
what does API stands 4????? plz reply asap thanks Application Program(ming) Interface.
A great source for this kind of questions http://en.wikipedia.org/wiki/Application_programming_interface I hope this helps, Cor <mohit.***@gmail.com> schrieb:
> what does API stands 4????? "Application 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/> Herfried,
> 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. Cor "Cor Ligthert [MVP]" <notmyfirstn***@planet.nl> schrieb: This doesn't mean it's not an API. API simply means "interface used to >> 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. 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/> Herfried K. Wagner [MVP] wrote:
Show quoteHide quote > "Cor Ligthert [MVP]" <notmyfirstn***@planet.nl> schrieb: Cor just loves to tease... ;-)> >> 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 :-). > > -- > M S Herfried K. Wagner > M V P <URL:http://dotnet.mvps.org/> > V B <URL:http://classicvb.org/petition/> 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 ?
Show quote
Hide quote
"Cerebrus" <zorg***@sify.com> schrieb: Framework simply means a set of libraries, tools, etc. which can be used to >> >> 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 >> :-). > > 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 ? 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/> Herfried,
> Framework simply means a set of libraries, tools, etc. which can be used I would not say it like that, it is a part of the OS where against the CLI > to develop applications, for example. 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 Show quoteHide quote "Herfried K. Wagner [MVP]" <hirf-spam-me-here@gmx.at> schreef in bericht news:ux3SyKjiGHA.4896@TK2MSFTNGP05.phx.gbl... > "Cerebrus" <zorg***@sify.com> schrieb: >>> >> 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 >>> :-). >> >> 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 ? > > 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/> "Cor Ligthert [MVP]" <notmyfirstn***@planet.nl> schrieb: The .NET Framework is not part of the OS. It's simply a layer that is built >> Framework simply means a set of libraries, tools, etc. which can be used >> to develop applications, for example. > > I would not say it like that, it is a part of the OS where against the CLI > code can run. on top of the OS core functionality. > In my opinion is it the same is for every layer from an OS. That does not It doesn't, but each layer can expose an API! Otherwise it would be > make them an API. impossible to develop drivers, normal applications, etc. for Windows. > The CLI code contains interfaces to that part of the OS but that does not I am not sure what exactly you are referring to with CLI (typically this > make it an API. stands for "Common Language Infrastructure"). > If you tell that inside this definition the classes distributed by the No, I do not claim that. As I mentioned before, I see APIs as something > development part of the framework are API's 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. > However that makes from every application itself almost an API. 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. > In my opinion is an API more restricted to one function from the OS. ?!?-- M S Herfried K. Wagner M V P <URL:http://dotnet.mvps.org/> V B <URL:http://classicvb.org/petition/> Herfried,
I stop this with exception from one. > I am not sure what exactly you are referring to with CLI (typically this For me this stands typically for "Cor Ligthert" (as often used abrivation).> stands for "Common Language Infrastructure"). > :-) Cormohit.***@gmail.com wrote:
>guys a stupid question..... These two guys are so funny - API = Application Programming Interface. >what does API stands 4????? >plz reply asap >thanks > > > 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 Tomb,
>> We both told that in our first reply, where I gave a link Wikepedi which > These two guys are so funny - API = Application Programming Interface. 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 tomb wrote:
> These two guys are so funny - API = Application Programming Interface. Rather simplifying it, aren't you ! I think both of our veteran> 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 specialists (I refrain from using the word "guys") have made such valid points that I'm now confused. But not that it matters much. 
Other interesting topics
Why Me? (Instead of Form1)
How do I increment a byte with out casting? Capturing mouse events (Mouse up and down on the desktop) How to walk through InnerExceptions? Help in saving database How to connect to database Threading in .Net... Edit Mode Process.start explorer in popup Shortening my source. |
|||||||||||||||||||||||
