swig/Examples
Vadim Zeitlin e8c6bfbc8f Remove completely broken handling of member function pointers
Member function pointers can't possibly be represented as function pointers,
they have a strictly bigger size and attempting to do it resulted in code
which, with a lot of bad casts, compiled, but crashed during run-time.

The proper solution is to represent C++ method pointers with an appropriate
opaque type, but for now this remains broken -- just make it explicitly broken
instead of pretending that it works when it actually has no chance to.

Let "namespace_spaces" unit test pass, as it's not really related to the
function pointers, by adding an explicit SWIGC test to it.
2016-04-21 01:37:40 +02:00
..
android Remove use of preinst-swig script 2015-08-21 22:43:17 +01:00
c No real changes, just convert files to Unix EOLs 2016-04-16 00:10:22 +02:00
chicken Remove use of preinst-swig script 2015-08-21 22:43:17 +01:00
contract Remove bogus ; after } in examples 2014-11-07 15:34:43 +13:00
csharp Remove use of preinst-swig script 2015-08-21 22:43:17 +01:00
d Remove use of preinst-swig script 2015-08-21 22:43:17 +01:00
go Remove use of preinst-swig script 2015-08-21 22:43:17 +01:00
guile Remove use of preinst-swig script 2015-08-21 22:43:17 +01:00
java Remove use of preinst-swig script 2015-08-21 22:43:17 +01:00
javascript Remove use of preinst-swig script 2015-08-21 22:43:17 +01:00
lua Correct to Unix CR/LF 2015-09-05 16:18:03 +01:00
modula3 More remove SWIG_LIB variable 2015-08-21 22:48:34 +01:00
mzscheme More remove SWIG_LIB variable 2015-08-21 22:48:34 +01:00
ocaml Remove use of preinst-swig script 2015-08-21 22:43:17 +01:00
octave octave: map unary functions to __...___ Python-style unary members 2016-02-07 20:22:39 +01:00
perl5 Remove use of preinst-swig script 2015-08-21 22:43:17 +01:00
php Remove use of preinst-swig script 2015-08-21 22:43:17 +01:00
pike Remove use of preinst-swig script 2015-08-21 22:43:17 +01:00
python Merge branch 'master' into C 2016-04-08 17:29:16 +02:00
r Remove use of preinst-swig script 2015-08-21 22:43:17 +01:00
ruby Ruby mark_function example and docs fixes 2015-09-05 15:30:50 +01:00
s-exp Remove use of preinst-swig script 2015-08-21 22:43:17 +01:00
scilab Revert "scilab: runtime initialization needed in examples" 2016-03-18 08:56:23 +00:00
tcl Remove use of preinst-swig script 2015-08-21 22:43:17 +01:00
test-suite Remove completely broken handling of member function pointers 2016-04-21 01:37:40 +02:00
xml More remove SWIG_LIB variable 2015-08-21 22:48:34 +01:00
index.html
Makefile.in Only syntax check generated header when not using run test 2016-04-21 01:37:40 +02:00
README Improve Examples/README 2014-02-21 08:14:24 +13:00

SWIG Examples

The subdirectories of "Examples" named after SWIG's language backends
contain a number of simple examples that are primarily used for testing.

The file 'index.html' is the top of a hyperlinked document that
contains information about all of the examples along with various
notes related to each example.

Note: All of the examples rely upon the Makefile in this directory.
You may need to edit it to reflect the configuration of your machine
in case the configure script guesses incorrect settings.


*** Special note concerning C++ ***

The configure script is currently unable to handle all of the possible
options for producing dynamically loadable C++ extensions.  Here are
the rules of thumb for making C++ work:

 -  Try using the C++ as the linker for the shared library.  For example:

         g++ -shared $(OBJS) -o module.so

 -  If that doesn't work, you may need to explicitly link against some
    kind of C++ runtime library.  For example:

         ld -G $(OBJS) -L/opt/SUNWspro/lib -lCrun -o module.so

    This can be set by modifying the setting of CPP_DLLIBS in the
    Makefile.


*** Special note for SWIG Maintainers ***

When you add an example, consider arranging for the example to be also
useful as part of the SWIG testing framework.  To do this, include in
the example makefile a target "check" ("check: all" is sufficient for a
first pass), and add an invocation to ../Makefile.in under target
"check-examples" (or whatever is appropriate).  Later, we can add or
expand the actions under target "check" to do more in-depth testing.