Foreign function interface
This article's use of external links may not follow Wikipedia's policies or guidelines. (August 2016) (Learn how and when to remove this template message)
A foreign function interface (FFI) is a mechanism by which a program written in one programming language can call routines or make use of services written in another.
The term comes from the specification for Common Lisp, which explicitly refers to the language features for inter-language calls as such; the term is also used officially by the Haskell and Python programming languages. Other languages use other terminology: the Ada programming language talks about "language bindings", while Java refers to its FFI as the JNI (Java Native Interface) or JNA (Java Native Access). Foreign function interface has become generic terminology for mechanisms which provide such services.
The primary function of a foreign function interface is to mate the semantics and calling conventions of one programming language (the host language, or the language which defines the FFI), with the semantics and conventions of another (the guest language). This process must also take into consideration the runtime environments and/or application binary interfaces of both. This can be done in several ways:
- Requiring that guest-language functions which are to be host-language callable be specified or implemented in a particular way; often using a compatibility library of some sort.
- Use of a tool to automatically "wrap" guest-language functions with appropriate glue code, which performs any necessary translation.
- Use of wrapper libraries
- Restricting the set of host language capabilities which can be used cross-language. For example, C++ functions called from C may not (in general) include reference parameters or throw exceptions.
FFIs may be complicated by the following considerations:
- If one language supports garbage collection (GC) and the other does not; care must be taken that the non-GC language code does nothing to cause GC in the other to fail. In JNI, for example, C code which "holds on to" object references that it receives from Java must "register" this fact with the Java runtime environment (JRE); otherwise, Java may delete objects before C has finished with them. (The C code must also explicitly release its link to any such object, as soon as there is no further need, by C, of that object.)
- Complicated or non-trivial objects or datatypes may be difficult to map from one environment to another.
- It may not be possible for both languages to maintain references to the same instance of a mutable object, due to the mapping issue above.
- One or both languages may be running on a virtual machine (VM); moreover, if both are, these will probably be different VMs.
- Cross-language inheritance and other differences, such as between type systems or between object-composition models, may be especially difficult.
Examples of FFIs include:
- Ada language bindings, allowing not only to call foreign functions but also to export its functions and methods to be called from non-Ada code.
- C++ has a trivial FFI with C, as the languages share a significant common subset. The primary effect of the extern "C" declaration in C++ is to disable C++ name mangling.
- Clean provides a bidirectional FFI with all languages following C or the stdcall calling convention.
- CNI, alternative to JNI used in the GNU compiler environment.
- D does it the same way as C++ does, with extern "C" through extern (C++)
- Dynamic languages, such as Python, Perl, Tcl, and Ruby, all provide easy access to native code written in C/C++ (or any other language obeying C/C++ calling conventions).
- Factor has FFIs for C, Fortran, Objective-C, and Windows COM; all of these enable importing and calling arbitrary shared libraries dynamically.
- The FFIs of Common Lisp and Haskell
- Fortran 2003 has a module ISO_C_BINDING which provides interoperable data types (both intrinsic types and POD structs), interoperable pointers, interoperable global data stores, and mechanisms for calling C from Fortran and for calling Fortran from C.
- Perl 6 can call Ruby, Python, Perl 5, Brainfuck, Lua, C, C++ and Scheme Guile/Gambit  
- Go can call C code directly via the
- JNI, which provides an interface between Java and C/C++, the preferred systems languages on most systems where Java is deployed. JNA provides an interface with native libraries without having to write glue code. Another example is JNR
- Julia has
ccallkeyword to call C (and other languages, e.g. Fortran); while packages, providing similar no-boilerplate support, are available for some languages e.g. for Python (to e.g. provide OO support and GC support), Java (and supports other JDK-languages, such as Scala) and R. Interactive use with C++ is also possible with Cxx.jl package.
- Python provides the ctypes and cffi modules. For example, the ctypes module can load C functions from shared libraries/DLLs on-the-fly and translate simple data types automatically between Python and C semantics as follows:
import ctypes libc = ctypes.CDLL( '/lib/libc.so.6' ) # under Linux/Unix t = libc.time(None) # equivalent C code: t = time(NULL) print t
- P/Invoke, which provides an interface between the Microsoft Common Language Runtime and native code.
- Racket has a native FFI based heavily on macros that enables importing arbitrary shared libraries dynamically.
- Rust also defines a foreign function interface.
- Visual Basic has a declarative syntax that allows it to call non-Unicode C functions.
- One of the bases of the Component Object Model is a common interface format, which natively uses the same types as Visual Basic for strings and arrays.
- LuaJIT, a just-in-time implementation of Lua, has an FFI that allows "calling external C functions and using C data structures from pure Lua code".
- Wolfram Language provides a technology called WSTP (Wolfram Symbolic Transfer Protocol) which enables bidirectional calling of code between other languages with bindings for C++, Java, .NET and other languages.
In addition, many FFIs can be generated automatically: for example, SWIG. However, in the case of an extension language a semantic inversion of the relationship of guest and host can occur, when a smaller body of extension language is the guest invoking services in the larger body of host language, such as writing a small plugin  for GIMP.
Some FFIs are restricted to free standing functions, while others also allow calls of functions embedded in an object or class (often called method calls); some even permit migration of complex datatypes and/or objects across the language boundary.
In most cases, a FFI is defined by a "higher-level" language, so that it may employ services defined and implemented in a lower level language, typically a systems language like C or C++. This is typically done to either access OS services in the language in which the OS' API is defined, or for performance considerations.
Many FFIs also provide the means for the called language to invoke services in the host language as well.
The term foreign function interface is generally not used to describe multi-lingual runtimes such as the Microsoft Common Language Runtime, where a common "substrate" is provided which enables any CLR-compliant language to use services defined in any other. (However, in this case the CLR does include an FFI, P/Invoke, to call outside the runtime.) In addition, many distributed computing architectures such as the Java remote method invocation (RMI), RPC, CORBA, SOAP and D-Bus permit different services to be written in different languages; such architectures are generally not considered FFIs.
There are some special cases, in which the languages compile into the same bytecode VM, like Clojure and Java, as well as Elixir and Erlang. Since there is no interface, it is not a FFI, strictly speaking, while it offers the same functionality to the user.
- Language interoperability
- Interface definition language
- Calling convention
- Name mangling
- Application programming interface
- Application binary interface
- Comparison of application virtual machines
- Remote procedure call
- "CFFI User Manual". common-lisp.org. Retrieved 2015-06-18.
- "FFI Introduction". HaskellWiki. Retrieved 19 June 2015.
Haskell's FFI is used to call functions from other languages (basically C at this point), and for C to call Haskell functions.
- "CFFI documentation". Retrieved 19 June 2015.
C Foreign Function Interface for Python. The goal is to provide a convenient and reliable way to call compiled C code from Python using interface declarations written in C.
- "Interface to Other Languages". Adaic.org. Retrieved 2013-09-29.
- "Foreign Export". Retrieved 2018-04-25.
- "Calling C From Clean". Retrieved 2018-04-25.
- "Inline implementations". Retrieved 2017-08-15.
- "Native Call". Retrieved 2017-08-15.
- "cgo — The Go Programming Language". Retrieved 2015-08-23.
- "Calling C and Fortran Code · The Julia Language". docs.julialang.org. Retrieved 2018-02-11.
- PyCall.jl: Package to call Python functions from the Julia language, JuliaPy, 2018-02-08, retrieved 2018-02-11
- Eli Barzilay. "The Racket Foreign Interface". Docs.racket-lang.org. Retrieved 2013-09-29.
- "TR600.pdf" (PDF). Retrieved 2013-09-29.
- https://doc.rust-lang.org/1.5.0/book/ffi.html. Retrieved 2017-08-07. Missing or empty
- Mike Pall. "FFI Library". Luajit.org. Retrieved 2013-09-29.
- "4. A sample script". Gimp.org. 2001-02-04. Retrieved 2013-09-29.
- "Script-Fu and plug-ins for The GIMP". Gimp.org. Retrieved 2013-09-29.
- c2.com: Foreign function interface
- Haskell 98 Foreign Function Interface
- Allegro Common Lisp FFI
- A Foreign Function Interface generator for occam-pi
- UFFI: Lisp Universal Foreign Function Interface
- CFFI: Common Foreign Function Interface, for Common Lisp
- Java Native Interface: Programmer's Guide and Specification
- The JNI Specification
- dyncall library using assembly call kernels for a variety of processors,OS and calling conventions