Editing Wrapper library
Appearance
Latest revision | Your text | ||
Line 81: | Line 81: | ||
Some wrapper libraries exist to act as a bridge between a client application and a library written using an incompatible technology. For instance, a [[Java (programming language)|Java]] application may need to execute a [[system call]]. However system calls are typically exposed as C library functions. To resolve this issue Java implements wrapper libraries which make these system calls callable from a Java application. |
Some wrapper libraries exist to act as a bridge between a client application and a library written using an incompatible technology. For instance, a [[Java (programming language)|Java]] application may need to execute a [[system call]]. However system calls are typically exposed as C library functions. To resolve this issue Java implements wrapper libraries which make these system calls callable from a Java application. |
||
In order to achieve this, languages like Java provide |
In order to achieve this, languages like Java provide mechanisms that make this possible. Some examples of these mechanisms include: |
||
* [[Java Native Interface|Java Native Interface (JNI)]] |
* [[Java Native Interface|Java Native Interface (JNI)]] |