From e4e0977bab9f7dc280c7ca2ade01b6cf9641dc64 Mon Sep 17 00:00:00 2001 From: John Lenz Date: Thu, 4 Nov 2004 01:35:36 +0000 Subject: [PATCH] Update Guile docs to reflect the change from -gh to -scm as default. git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk/SWIG@6653 626c5289-ae23-0410-ae9c-e8d60b6d4f22 --- Doc/Manual/Guile.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Doc/Manual/Guile.html b/Doc/Manual/Guile.html index b32239dee..57187cd11 100644 --- a/Doc/Manual/Guile.html +++ b/Doc/Manual/Guile.html @@ -57,12 +57,12 @@ we explicitly prefix the context, e.g., "guile-module".

The guile module can currently export wrapper files that use the guile GH interface or the SCM interface. This is controlled by an argument passed to swig. The "-gh" argument causes swig -to output GH code, and the "-scm" argument causes swig to output SCM code. Right now the "-gh" argument +to output GH code, and the "-scm" argument causes swig to output SCM code. Right now the "-scm" argument is the default. The "-scm" wrapper generation assumes a guile version >= 1.6 and has several advantages over the "-gh" wrapper generation including garbage collection and GOOPS support. -The "-gh" wrapper generation can be used for older versions of guile. Thus eventually -the guile GH wrapper code generation will be depreciated (as guile 1.6 and above become more common) and the -SCM interface will become the default. The SCM and GH interface differ greatly in how they store +The "-gh" wrapper generation can be used for older versions of guile. +The guile GH wrapper code generation is depreciated and the +SCM interface is the default. The SCM and GH interface differ greatly in how they store pointers and have completely different run-time code. See below for more info.

The GH interface to guile is deprecated. Read more about why in the