SWIG is a software development tool that connects programs written in C and C++ with a variety of high-level programming languages.
http://www.swig.org
c45ce46c51
Why did you remove the INPUT/OUTPUT/BOTH typemaps in revision 1.3 of
Lib/guile/typemaps.i? They seem to be standard in SWIG, as they are
present in the other language modules, and everyone needs them. I
suggest you put them back in.
Lib/exception.i, Source/Modules1.1/guile.cxx: I have written the
Guile-specific code for Lib/exception.i, which implements
SWIG_exception as a macro calling _SWIG_exception, which is defined in
the same file. The SWIG_*Error constants are mapped to Guile error
symbols, which are passed to scm_error. The macro uses the
preprocessor macro SCHEME_NAME, which is set at the beginning of the
function wrapper code by a modified Source/Modules1.1/guile.cxx. Here
is a test (with array.i):
(int-get '() 0) ==> signals swig-value-error
Moreover, I fixed a type-lookup bug in Lib/guile/guile.swg when
compiled -with-smobs, which had crept in from swigptr.swg. Here is a
test (again with array.i):
(define c (int-array 5))
(int-get c 0) ==> must not signal a wrong-type error
Lib/guile/guiledec.swg, Source/Modules1.1/guile.cxx: Use the
SWIG_NOINCLUDE preprocessor symbol to indicate that SWIG runtime
functions are imported from a different module, as it is done in other
language modules.
(SWIG_init) Make this function globally visible only in simple linkage
(the user should rename the function by a #define in this case). In
other linkages, having SWIG_init globally visible (in multiple
modules) just makes trouble.
Source/Modules1.1/guile.cxx (GUILE::link_variable) Printf the C
string, not the String class.
Source/SWIG1.1/swig11.h, Source/SWIG1.1/sstring.cxx: Constified two
operator arguments, to get rid of warnings issued by the SUNWSpro
C++ compiler.
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@417 626c5289-ae23-0410-ae9c-e8d60b6d4f22
|
||
|---|---|---|
| SWIG | ||