Lines Matching full:para
5 <para>
9 <listitem><para>object-oriented C-based APIs and</para></listitem>
10 <listitem><para>automatic transparent API bindings to other compiled
11 or interpreted languages.</para></listitem>
13 </para>
15 <para>
20 </para>
22 <para>
28 </para>
33 <para>
38 </para>
40 <para>
47 </para>
49 <para>
62 </para>
69 <para>
75 </para>
77 <para>
83 </para>
85 <para>
107 </para>
109 <para>
113 <listitem><para>Find where the function is located. This probably means finding the binary generated by the C compiler
114 which exports this function.</para></listitem>
115 <listitem><para>Load the code of the function in executable memory.</para></listitem>
116 <listitem><para>Convert the Python parameters to C-compatible parameters before calling
117 the function.</para></listitem>
118 <listitem><para>Call the function with the right calling convention.</para></listitem>
119 <listitem><para>Convert the return values of the C function to Python-compatible
120 variables to return them to the Python code.</para></listitem>
122 </para>
124 <para>
128 <listitem><para>The first solution is to write by hand a lot of glue code, once for each function exported or imported,
131 C functions.</para></listitem>
132 <listitem><para>Another, nicer solution is to automatically generate the glue code, once for each function exported or
134 reads the original function signature.</para></listitem>
135 <listitem><para>The solution used by GLib is to use the GType library which holds at runtime a description of
138 <para>
146 </para>
149 function calling conventions between different runtime domains.</para></listitem>
167 </para>
169 <para>
175 </para>
