Mercurial > pub > dyncall > dyncall

comparison doc/manual/manual_dyncall_api.tex @ 360:32736025371f

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
- doc updates with more info about signature string usage
author Tassilo Philipp
date Mon, 13 Apr 2020 21:35:43 +0200
parents 6e33db95e724
children 78dfa2f9783a
comparison
equal deleted inserted replaced
359:e8a13c880399 360:32736025371f
285 285
286 \paragraph{Details} 286 \paragraph{Details}
287 287
288 These functions can be used to operate \product{dyncall} via a printf-style 288 These functions can be used to operate \product{dyncall} via a printf-style
289 functional interface, using a signature string encoding the argument types and 289 functional interface, using a signature string encoding the argument types and
290 return type. 290 return type (and optionally also the calling convention used).
291 \capi{dcArgF()} and \capi{dcVArgF()} just bind arguments to the \capi{DCCallVM} 291 \capi{dcArgF()} and \capi{dcVArgF()} just bind arguments to the \capi{DCCallVM}
292 object, so any return value specified in the signature is ignored. \capi{dcCallF()} 292 object, so any return value specified in the signature is ignored. \capi{dcCallF()}
293 and \capi{dcVCallF()} also take a function pointer to call after binding the arguments. 293 and \capi{dcVCallF()} also take a function pointer to call after binding the arguments.
294 The return value will be stored in what \lstinline{result} points to. 294 The return value will be stored in what \lstinline{result} points to.
295 For more information about the signature format, refer to \ref{sigchar}. 295 For more information about the signature format, refer to \ref{sigchar}.