FACTOID # 91: In the Maldives, there are more than 2 jails for every 1000 people.
 
 Home   Encyclopedia   Statistics   Countries A-Z   Flags   Maps   Education   Forum   FAQ   About 
 
WHAT'S NEW
RECENT ARTICLES
More Recent Articles »
 

SEARCH ALL

FACTS & STATISTICS    Advanced view

Search encyclopedia, statistics and forums:

 

 

(* = Graphable)

 

 


Encyclopedia > Interface definition language

An interface description language, (alternatively interface definition language) (IDL), is a computer language or simple syntax for describing the interface of a software component. It is essentially a common language for writing the "manual" on how to use a piece of software from another piece of software, in much the same fashion that a user manual describes how to use a piece of software to the user.


IDLs are used in situations where the software on either side may not share common "call semantics", referring to the way the computer language "talks" to the routines. For instance, C and Pascal have different ways of calling routines, and in general cannot call code written in the other language. IDLs are a subset of both, a general language to which both can conform to enable language-independent code.


IDLs are most commonly found in software intended to allow routines to be called on other machines, known as remote procedure call. In these cases the call semantics may vary not only between languages, but also due to the architecture of the machines themselves.


An IDL is part of the Distributed Computing Environment, COM, SOM, XPCOM (also known as XPIDL), CORBA, and SOAP for Web Services.


See also

Major programming languages (more)

Ada | ALGOL | APL | AWK | BASIC | C | C++ | C# | COBOL | Delphi | Eiffel | Fortran | Haskell | IDL | Java | JavaScript | Lisp | LOGO | ML | Objective-C | Pascal | Perl | PHP | PL/I | Prolog | Python | Ruby | SAS | Scheme | sh | Simula | Smalltalk | SQL | Visual Basic


  Results from FactBites:
 
Automated schema and interface generation - Patent 6631519 (5922 words)
Appendix D illustrates two exemplary IDL files produced by an embodiment of the invention using the schema definition shown in Appendix A. The source code 230 and the interface definition 232 are input to compiler 240, which translates the input files to object code modules defining component objects 242.
Because the interface methods and properties in the components are generated from the same source as the database table definitions themselves, there is no chance for incompatibility between the object methods and properties in the components and the data objects in the database.
The schema definition data, in an embodiment of the invention, is expressed in the XML language.
  More results at FactBites »


 

COMMENTARY     


Share your thoughts, questions and commentary here
Your name
Your comments
Please enter the 5-letter protection code

Want to know more?
Search encyclopedia, statistics and forums:

 


Lesson Plans | Student Area | Student FAQ | Reviews | Press Releases |  Feeds | Contact
The Wikipedia article included on this page is licensed under the GFDL.
Images may be subject to relevant owners' copyright.
All other elements are (c) copyright NationMaster.com 2003-5. All Rights Reserved.
Usage implies agreement with terms.