aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rwxr-xr-xdoc/manual/index.html13
1 files changed, 9 insertions, 4 deletions
diff --git a/doc/manual/index.html b/doc/manual/index.html
index 50fe71b..075ffe5 100755
--- a/doc/manual/index.html
+++ b/doc/manual/index.html
@@ -1551,10 +1551,7 @@ code generation. Defaults to false.
(optional) Indicates that a ProcAddressTable entry should be produced
for the specified function even though it does not have an associated
-function pointer typedef in the header. This directive does not
-currently cause the autogenerated Java and C code to change to
-call-through-function-pointer style, which should probably be
-considered a bug. (FIXME)
+function pointer typedef in the header.
<dt><strong><a name="GetProcAddressTableExpr">GetProcAddressTableExpr</a></strong>
@@ -1575,6 +1572,14 @@ separate class accessed via static methods, so one of the associated
directives is <code>GetProcAddressTableExpr
ALProcAddressLookup.getALCProcAddressTable()</code>.
+<dt><strong><a name="LocalProcAddressCallingConvention">LocalProcAddressCallingConvention</a></strong>
+<dd> Syntax: <code>LocalProcAddressCallingConvention [function name] [calling convention string]</code> <br>
+
+(optional) For the given function whose glue code generation is
+affected by a <CODE>ForceProcAddressGen</CODE> directive, this
+specifies the calling convention of the locally generated function
+pointer typedef. This is needed only on Windows and only for APIs
+whose calling convention differs from the default __cdecl.
<dt><strong><a name="ProcAddressNameExpr">ProcAddressNameExpr</a></strong>
<dd> Syntax: <code>ProcAddressNameExpr [expression]</code> <br>