pkgsrc/devel/g-wrap/DESCR
wiz b8bdace7b4 Update to 1.9.3, from Greg Troxel via pkgsrc-wip.
Changes since 1.3.4:

Version 1.9.3

  - Comes with a compatibility layer that allows GnuCash to be built
    with it.

  - Reverts the enhanced generics support, which was introduced in
    1.9.2, since that currently breaks guile-gnome

  - Bugfixes
    + g-wrap-2.0-guile.pc is now generated correctly, even if the
      internal libffi is used.
    + Types used by constants are now considered when calculating the
      set of referenced types in a wrapset. This bug led to missing code
      and compile errors when a type defined in another wrapset was used
      by only by a constant.
    + On platforms which lack alloca(), the version shipped with
      G-Wrap should now build correctly.

Version 1.9.2

  - Now comes with libffi included, for systems which lack an libffi
    installation

  - SRFI module checks now work correctly, even if you do an in-tree build

Version 1.9.1

 - API change: destruct-value-cg is now named destroy-value-cg

 - Bugfixes
   + A bug in the latent generic code has been fixed
   + The error message for WCP type errors has been fixed

Version 1.9.0

 - Complete rewrite; too many changes to list, see the manual for the
   new GOOPS-based API and the guile-gnome project for an extended
   example.

  - New features:
    + Output arguments
    + Default arguments

  - G-Wrap should be target-language agnostic, like it was in its
    early days.
2004-12-03 17:06:58 +00:00

17 lines
630 B
Text

G-Wrap is a tool (and Guile library) for generating function wrappers
for inter-language calls. It currently only supports generating Guile
wrappers for C functions.
This package provides G-Wrap TNG (to be 2.0), with the following
goals:
* Use GOOPS, for enhanced flexibility
* Get rid of the cruft that has accumulated, simplify where possible
without sacrificing features
* Be target-language agnostic; i.e. clean separation of the core and
e.g. the Guile-specific code. New languages (perhaps even
non-Schemes) should be easy to add.
* Offer the current (1.3.4+) wrapping API as a compatibility layer.