dido:public:ra:xapend:xapend.b_stds:tech:omg:idl
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:tech:omg:idl [2020/05/05 20:49] nick ↷ Links adapted because of a move operation |
dido:public:ra:xapend:xapend.b_stds:tech:omg:idl [2021/08/17 15:19] (current) murphy [Scope] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== OMG: Interface Definition Language (IDL) ===== | ===== OMG: Interface Definition Language (IDL) ===== | ||
| - | [[dido:public:apdx.stds:tech:omg| return to the OMG Standards ]] | + | [[dido:public:ra:xapend:xapend.b_stds:tech:omg:start| return to the OMG Standards ]] |
| <table> | <table> | ||
| Line 16: | Line 16: | ||
| | | ||
| ==== Scope ==== | ==== Scope ==== | ||
| - | : //This document specifies the OMG Interface Definition Language (IDL). IDL is a descriptive language used to define data types and interfaces in a way that is independent of the programming language or operating system/processor platform.// | + | : //This document specifies the OMG Interface Definition Language (IDL). IDL is a descriptive language used to define data types and [[dido:public:ra:xapend:xapend.a_glossary:i:interface|interfaces]] in a way that is independent of the [[dido:public:ra:xapend:xapend.a_glossary:p:programlang|programming language]] or [[dido:public:ra:xapend:xapend.a_glossary:o:os|operating system]]/[[dido:public:ra:xapend:xapend.a_glossary:p:processor|processor]] [[dido:public:ra:xapend:xapend.a_glossary:p:platform|platform]].// |
| - | ://The IDL specifies only the syntax used to define the data types and interfaces. It is normally used in connection with other specifications that further define how these types/interfaces are utilized in specific contexts and platforms:// | + | ://The IDL specifies only the [[dido:public:ra:xapend:xapend.a_glossary:s:syntax|syntax]] used to define the data types and interfaces. It is normally used in connection with other specifications that further define how these types/interfaces are utilized in specific contexts and platforms:// |
| * //Separate “language mapping” specifications define how the IDL-defined constructs map to specific | * //Separate “language mapping” specifications define how the IDL-defined constructs map to specific | ||
| programming languages, such as, C/C++, Java, C#, etc.// | programming languages, such as, C/C++, Java, C#, etc.// | ||
| * //Separate “serialization” specifications define how data objects and method invocations are serialized into a | * //Separate “serialization” specifications define how data objects and method invocations are serialized into a | ||
| format suitable for network transmission.// | format suitable for network transmission.// | ||
| - | * //Separate “middleware” specifications, such as, DDS or CORBA leverage the IDL to define data-types, services, and interfaces. The description of IDL grammar uses a syntax notation that is similar to Extended Backus-Naur Format (EBNF).// | + | * //Separate “[[dido:public:ra:xapend:xapend.a_glossary:m:midware|middleware]]” specifications, such as, DDS or [[dido:public:ra:xapend:xapend.a_glossary:c:corba|CORBA]] leverage the IDL to define data-types, services, and interfaces. The description of IDL grammar uses a syntax notation that is similar to Extended Backus-Naur Format (EBNF).// |
| + | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
| + | /* To add a discussion page to this page, comment out the line that says | ||
| + | ~~DISCUSSION:off~~ | ||
| + | */ | ||
| + | ~~DISCUSSION:on|Outstanding Issues~~ | ||
| + | ~~DISCUSSION:off~~ | ||
dido/public/ra/xapend/xapend.b_stds/tech/omg/idl.1588726172.txt.gz · Last modified: 2020/05/05 20:49 by nick
