08:16 Baptiste Daroussin (bapt) 

MAN?PREFIX: eleminate its usage  and move man to share/man

    1b819e4

17:12 Li-Wen Hsu (lwhsu)  Author: Tassilo Philipp

devel/dyncall: Update to 1.3

PR:		260491

    519bf90

20:59 fernape 

Update devel/dyncall to 1.0

PR:	227737
Reported by:	tphilipp@potion-studios.com (maintainer)
Approved by:	tcberner (mentor)
Differential Revision:	https://reviews.freebsd.org/D15213

 

17:11 rakuco 

Update to 0.9.

PR:		205872
Submitted by:	Tassilo Philipp <tphilipp@potion-studios.com> (maintainer)

 

12:50 pawel 

Update to version 0.8

PR:		ports/187913
Submitted by:	maintainer

 

08:37 ehaupt 

Support staging

 

04:25 miwi 

- Update to 0.7

PR:             164611
Submitted by:   maintainer

11:50 decke 

- Update to 0.6
- Master sites updated

PR:             ports/150943
Submitted by:   Tassilo Philipp <tphilipp at potion-studios dot com>
(maintainer)
Approved by:    beat (co-mentor)

19:39 amdmi3 

- Update to 0.5

PR:             143672
Submitted by:   "Tassilo Philipp" <tphilipp@potion-studios.com> (maintainer)

00:47 clsung 

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>