2012-02-07 05:25:40 +01:00
|
|
|
include/dyncall.h
|
2010-09-28 13:50:47 +02:00
|
|
|
include/dyncall_alloc_wx.h
|
2012-02-07 05:25:40 +01:00
|
|
|
include/dyncall_args.h
|
2016-01-05 18:11:57 +01:00
|
|
|
include/dyncall_args_arm32_arm.h
|
|
|
|
|
include/dyncall_args_arm32_thumb.h
|
|
|
|
|
include/dyncall_args_mips.h
|
|
|
|
|
include/dyncall_args_ppc32.h
|
|
|
|
|
include/dyncall_args_ppc64.h
|
|
|
|
|
include/dyncall_args_sparc32.h
|
|
|
|
|
include/dyncall_args_sparc64.h
|
|
|
|
|
include/dyncall_args_x64.h
|
|
|
|
|
include/dyncall_args_x86.h
|
|
|
|
|
include/dyncall_callback.h
|
|
|
|
|
include/dyncall_callback_arm32_arm.h
|
|
|
|
|
include/dyncall_callback_arm32_thumb.h
|
|
|
|
|
include/dyncall_callback_mips.h
|
|
|
|
|
include/dyncall_callback_ppc32.h
|
|
|
|
|
include/dyncall_callback_ppc64.h
|
|
|
|
|
include/dyncall_callback_sparc32.h
|
|
|
|
|
include/dyncall_callback_x64.h
|
|
|
|
|
include/dyncall_callback_x86.h
|
|
|
|
|
include/dyncall_callf.h
|
|
|
|
|
include/dyncall_config.h
|
|
|
|
|
include/dyncall_macros.h
|
|
|
|
|
include/dyncall_signature.h
|
|
|
|
|
include/dyncall_thunk.h
|
|
|
|
|
include/dyncall_thunk_arm32_arm.h
|
|
|
|
|
include/dyncall_thunk_arm32_thumb.h
|
|
|
|
|
include/dyncall_thunk_arm64.h
|
|
|
|
|
include/dyncall_thunk_mips.h
|
|
|
|
|
include/dyncall_thunk_ppc32.h
|
|
|
|
|
include/dyncall_thunk_ppc64.h
|
|
|
|
|
include/dyncall_thunk_sparc32.h
|
|
|
|
|
include/dyncall_thunk_sparc64.h
|
|
|
|
|
include/dyncall_thunk_x64.h
|
2010-02-09 20:39:30 +01:00
|
|
|
include/dyncall_thunk_x86.h
|
2016-01-05 18:11:57 +01:00
|
|
|
include/dyncall_types.h
|
|
|
|
|
include/dyncall_value.h
|
|
|
|
|
include/dynload.h
|
The dyncall library encapsulates architecture-, OS- and compiler-specific
function call semantics in a virtual "bind parameters from left to right
and then call" interface allowing programmers to call C functions in a
completely dynamic manner. In other workds, instead of calling a function
directly, the dyncall library provides a mechanism to push the function
parameters manually and to issue the call afterwards.
This means, that a program can determine at runtime what function to
call, and what parameters to pass to it. The library is written in C and
assembly and provides a very simple C interface to program against.
The library comes in very handy to power flexible message systems,
dynamic function call dispatch mechanisms, closure implementations or
even to bridge different programming languages.
When it comes to language bindings, the dyncall library provides a clean
and portable C interface to dynamically issue calls to foreign code using
small kernels written in assembly. Instead of providing code for every
bridged function call, which unnecessarily results in code bloat, only a
couple of instructions are used to invoke every possible call.
WWW: http://www.dyncall.org
PR: ports/122720
Submitted by: Tassilo Philipp <tphilipp at potion-studios.com>
2008-04-14 02:47:00 +02:00
|
|
|
lib/libdyncall_s.a
|
2010-02-09 20:39:30 +01:00
|
|
|
lib/libdyncallback_s.a
|
The dyncall library encapsulates architecture-, OS- and compiler-specific
function call semantics in a virtual "bind parameters from left to right
and then call" interface allowing programmers to call C functions in a
completely dynamic manner. In other workds, instead of calling a function
directly, the dyncall library provides a mechanism to push the function
parameters manually and to issue the call afterwards.
This means, that a program can determine at runtime what function to
call, and what parameters to pass to it. The library is written in C and
assembly and provides a very simple C interface to program against.
The library comes in very handy to power flexible message systems,
dynamic function call dispatch mechanisms, closure implementations or
even to bridge different programming languages.
When it comes to language bindings, the dyncall library provides a clean
and portable C interface to dynamically issue calls to foreign code using
small kernels written in assembly. Instead of providing code for every
bridged function call, which unnecessarily results in code bloat, only a
couple of instructions are used to invoke every possible call.
WWW: http://www.dyncall.org
PR: ports/122720
Submitted by: Tassilo Philipp <tphilipp at potion-studios.com>
2008-04-14 02:47:00 +02:00
|
|
|
lib/libdynload_s.a
|
2014-02-19 09:37:53 +01:00
|
|
|
man/man3/dyncall.3.gz
|
2014-03-30 14:50:11 +02:00
|
|
|
man/man3/dyncallback.3.gz
|
|
|
|
|
man/man3/dynload.3.gz
|
