view doc/manual/manual_dyncallback_api.tex @ 533:71c884e610f0

- integration of patches from Raphael Luba, Thekla, Inc.: * integration of aggregate-by-value (struct, union) support patch for x64 (win and sysv) * windows/x64 asm additions to specify how stack unwinds (help for debuggers, exception handling, etc.) * see Changelog for details - new calling convention modes for thiscalls (platform agnostic, was specific before) * new signature character for platform agnostic thiscalls ('*' / DC_SIGCHAR_CC_THISCALL) - dcCallF(), dcVCallF(), dcArgF() and dcVArgF(): * added support for aggregates-by-value (wasn't part of patch) * change that those functions don't implicitly call dcReset() anymore, which was unflexible (breaking change) - added macros to feature test implementation for aggregate-by-value and syscall support - changed libdyncall_s.lib and libdyncallback_s.lib order in callback test makefiles, as some toolchains are picky about order - doc: * man page updates to describe aggregate interface * manual overview changes to highlight platforms with aggregate-by-value support - test/plain: replaced tests w/ old/stale sctruct interface with new aggregate one
author Tassilo Philipp
date Thu, 21 Apr 2022 13:35:47 +0200
parents 17287342e273
children
line wrap: on
line source

%//////////////////////////////////////////////////////////////////////////////
%
% Copyright (c) 2007,2013-2022 Daniel Adler <dadler@uni-goettingen.de>, 
%                              Tassilo Philipp <tphilipp@potion-studios.com>
%
% Permission to use, copy, modify, and distribute this software for any
% purpose with or without fee is hereby granted, provided that the above
% copyright notice and this permission notice appear in all copies.
%
% THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
% WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
% MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
% ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
% WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
% ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
% OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
%
%//////////////////////////////////////////////////////////////////////////////

\section{\emph{Dyncallback} C library API}

See the dyncallback(3) manpage for more information.

%@@@ removed, as manpages are more precise and up to date ------------------->
%
%This library extends \product{dyncall} with function callback support, allowing
%the user to dynamically create a callback object that can be called directly,
%or passed to functions expecting a function-pointer as argument.\\
%\\
%Invoking a \product{dyncallback} calls into a user-defined unified handler that 
%permits iteration and thus dynamic handling over the called-back-function's
%parameters.\\
%\\
%The flexibility is constrained by the set of supported types, though.\\
%\\
%For style conventions and supported types, see \product{dyncall} API section.
%In order to use \product{dyncallback}, include {\tt "dyncall\_callback.h"}.
%
%\subsection{Callback Object}
%
%The \emph{Callback Object} is the core component to this library.
%
%\paragraph{Types}
%
%\begin{lstlisting}[language=c]
%typedef struct DCCallback DCCallback;
%\end{lstlisting}
%
%\paragraph{Details}
%The \emph{Callback Object} is an object that mimics a fully typed function
%call to another function (a generic callback handler, in this case).\\
%\\
%This means, a pointer to this object is passed to a function accepting a pointer
%to a callback function \emph{as the very callback function pointer itself}.
%Or, if called directly, cast a pointer to this object to a function pointer and
%issue a call.
%
%
%\subsection{Allocation}
%
%\paragraph{Functions}
%
%\begin{lstlisting}[language=c]
%DCCallback* dcbNewCallback(const DCsigchar*   signature,
%                           DCCallbackHandler* funcptr,
%                           void*              userdata,
%                           DCaggr**           aggrs);
%void dcbFreeCallback(DCCallback* pcb);
%\end{lstlisting}
%
%\lstinline{dcbNewCallback} creates and initializes a new \emph{Callback} object,
%where \lstinline{signature} is the needed function signature (format is the
%one outlined in the language bindings-section of this manual, see Table \ref{sigchar})
%of the function to mimic, \lstinline{funcptr} is a pointer to a callback handler,
%and \lstinline{userdata} a pointer to custom data that might be useful in the
%handler.
%Use \lstinline{dcbFreeCallback} to destroy the \emph{Callback} object.\\
%\\
%As with \capi{dcNewCallVM}/\capi{dcFree}, this will allocate memory using the
%system allocators or custom overrides.
%
%
%\subsection{Callback handler}
%
%The unified callback handler's declaration used when creating a \capi{DCCallback}
%is:
%
%\begin{lstlisting}
%DCsigchar cbHandler(DCCallback* cb,
%                    DCArgs*     args,
%                    DCValue*    result,
%                    void*       userdata);
%\end{lstlisting}
%
%\capi{cb} is a pointer to the \capi{DCCallback} object in use, \capi{args} allows
%for dynamic iteration over the called-back-function's arguments (input) and
%\capi{result} is a pointer to a \capi{DCValue} object in order to store the
%callback's return value (output, to be set by handler).\\
%Finally, \capi{userdata} is a pointer to some user defined data that can be
%set when creating the callback object.
%The handler itself returns a signature character (see Table \ref{sigchar}) specifying the
%data type used for \capi{result}.
%