f0063afa71
* Due to the org-babel bug which breaks Python source code examples beyond the most simple snippets, ported the HOWTO to a source format which I *know* for sure won't break it. * Details of the org-mode bug is in https://dev.gnupg.org/T3977 * DITA project uses DITA-OT 2.x (2.4 or 2.5, IIRC) with support for DITA 1.3. * source files were written with oXygenXML Editor 20.0, hence the oXygenXML project file in the directory; however only the .ditamap and .dita files are required to generate any output with the DITA-OT. Signed-off-by: Ben McGinnes <ben@adversary.org>
18 lines
977 B
XML
18 lines
977 B
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE dita PUBLIC "-//OASIS//DTD DITA Composite//EN" "ditabase.dtd">
|
|
<dita>
|
|
<topic id="topic_jrb_pxx_5db">
|
|
<title>A C API</title>
|
|
<body>
|
|
<p>Unlike many modern APIs with which programmers will be more familiar with these days,
|
|
the GPGME API is a C API. The API is intended for use by C coders who would be able to
|
|
access its features by including the =gpgme.h= header file with their own C source code and
|
|
then access its functions just as they would any other C headers.</p>
|
|
<p>This is a very effective method of gaining complete access to the API and in the most
|
|
efficient manner possible. It does, however, have the drawback that it cannot be directly
|
|
used by other languages without some means of providing an interface to those languages.
|
|
This is where the need for bindings in various languages stems.</p>
|
|
</body>
|
|
</topic>
|
|
</dita>
|