changeset 795:23271902921a

replace ABI by more adequate FFI
author Sebastien Jodogne <s.jodogne@gmail.com>
date Mon, 06 Dec 2021 13:19:11 +0100
parents e22c1284ea0e
children 7078e6e35580
files Sphinx/source/developers/creating-plugins.rst
diffstat 1 files changed, 5 insertions(+), 3 deletions(-) [+]
line wrap: on
line diff
--- a/Sphinx/source/developers/creating-plugins.rst	Mon Dec 06 13:13:31 2021 +0100
+++ b/Sphinx/source/developers/creating-plugins.rst	Mon Dec 06 13:19:11 2021 +0100
@@ -18,8 +18,10 @@
 <https://hg.orthanc-server.com/orthanc/file/Orthanc-1.9.7/OrthancServer/Plugins/Include/orthanc/OrthancCPlugin.h>`__.
 As a consequence, an Orthanc plugin will typically be written using C
 or C++, although it is also possible to create native plugins using
-languages that feature compatibility with C headers and with C ABI
-(such as Rust or Objective-C).
+languages that feature compatibility with C headers and with `FFI of
+the C language
+<https://en.wikipedia.org/wiki/Foreign_function_interface>`__ (such as
+Rust or Objective-C).
 
 For developers who are more familiar with Python, it is also possible
 to create plugins using this simpler language. Check out the
@@ -67,7 +69,7 @@
 
 A plugin takes the form of a shared library (``.DLL`` under Windows,
 ``.so`` under GNU/Linux, ``.dylib`` under Apple OS X...) that uses the
-`ABI of the C language
+`FFI of the C language
 <https://en.wikipedia.org/wiki/Application_binary_interface>`__ to
 declare 4 public functions/symbols: