swig/Examples
Olly Betts c417250b4e [php] Allow testing if an object is SWIG-wrapped
Since the switch to wrapping classes using PHP's C API, we now
internally need to be able to tell if a PHP object is of or derived
from a class that is wrapped by SWIG so we know if we can offset the
zend_object pointer to get to the swig_object_wrapper.  If we try to
do this to an object which isn't wrapped by SWIG then we invoke C/C++
undefined behaviour (and typically get a segmentation fault).

This check is implemented by having a SWIG\wrapped empty interface which
we make all SWIG-wrapped classes implement simply so we can test for it
to detect such classes.

Fixes #2125
2022-01-20 14:42:02 +13:00
..
android
csharp
d
go Fix all Go tests to build with "go build" 2019-08-08 14:30:50 -07:00
guile Fix guile examples for C11 and later conformance 2021-11-15 19:25:41 +00:00
java Java 9 deprecation warning fixes for test-suite and examples 2019-02-21 13:47:39 -08:00
javascript Fix testcase -Wstringop-truncation warning in gcc11 2021-11-12 19:00:20 +00:00
lua Fix testcase -Wstringop-truncation warning in gcc11 2021-11-12 19:00:20 +00:00
mzscheme Remove use of std::bind2nd which is removed in C++17 2019-06-27 07:40:49 +01:00
ocaml [S-EXP] Remove code for Common Lisp S-Exp 2021-05-16 08:42:39 +12:00
octave Alphabetise testing of examples 2020-08-13 20:07:10 +01:00
perl5
php Fix and restore disabled code in PHP value example 2021-05-04 14:21:13 +12:00
python Update Python tests to not use flatstaticmethod access 2022-01-14 22:48:11 +00:00
r
ruby Remove use of std::bind2nd which is removed in C++17 2019-06-27 07:40:49 +01:00
scilab Alphabetise testing of examples 2020-08-13 20:07:10 +01:00
tcl Remove use of std::bind2nd which is removed in C++17 2019-06-27 07:40:49 +01:00
test-suite [php] Allow testing if an object is SWIG-wrapped 2022-01-20 14:42:02 +13:00
xml
index.html
Makefile.in [Allegrocl] Remove code for Allegro Common Lisp 2021-05-13 10:38:40 +12:00
README

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.