swig/Examples
Paweł Tomulik 5562deec62 Fixed SF bug #1297 (Python imports)
This changeset resolves several issues related to python imports.
For example, it's possible now to import modules having same module
names, but belonging to different packages.

From the user's viewpoint, this patch gives a little bit more control on
import directives generated by swig. The user may choose to use relative
or absolute imports (docs are provided in separate PR).

Some details:
  - we (still) generate import directives in form 'import a.b.c' which
    corresponds to absolute imports in python3 and (the only available)
    ambiguous one in python2.
  - added -relativeimport option to use explicit relative import syntax
    (python3),

Tests are under Examples/python, these are in fact regression tests but
with the current swig testing framework it seems to be impossible to put
appropriate tests under test-suite.

Closes #7
2013-12-24 17:22:25 +00:00
..
android Fix typos 2013-09-25 17:29:33 +12:00
chicken Chicken - make check-examples run like other examples - not all run very well though! 2013-04-20 02:28:48 +01:00
contract fix extern declarations 2005-06-28 21:14:24 +00:00
csharp Add C++ nested class example 2013-11-30 09:23:16 +00:00
d Fix gcc -Waddress warning in variables examples 2013-10-18 06:53:02 +01:00
go In Examples/Makefile.in, compile and link the program in go and 2013-12-20 08:14:45 -08:00
guile Guile port example fix for Guile 2.0 2013-05-23 23:24:19 +01:00
java Add C++ nested class example 2013-11-30 09:23:16 +00:00
lua Fix gcc -Waddress warning in variables examples 2013-10-18 06:53:02 +01:00
modula3 Modula3 makefiles tweaks for consistency with other languages - they still don't work though 2013-04-19 22:47:28 +01:00
mzscheme Mzscheme - fix for running examples during 'make check-examples' - they don't run very well though\! 2013-04-20 02:28:48 +01:00
ocaml Ocaml example makefiles tweaks for consistency with other languages. Attempt to add runtime tests to 'make check' - untested. 2013-04-19 22:47:28 +01:00
octave Fix gcc -Waddress warning in variables examples 2013-10-18 06:53:02 +01:00
perl5 Change the length of strings created from fixed-size buffers. 2013-12-23 21:12:17 +00:00
php Fix Examples/php/pointer to work with PHP 5.5 2013-12-12 15:52:51 +13:00
pike Pike - a few updates to get Pike 7.8 running most of the examples 2013-04-20 02:28:48 +01:00
python Fixed SF bug #1297 (Python imports) 2013-12-24 17:22:25 +00:00
r R examples makefile tidyup 2013-04-19 22:47:26 +01:00
ruby Fix gcc -Waddress warning in variables examples 2013-10-18 06:53:02 +01:00
s-exp remove final vestiges of gifplot example 2010-02-28 00:16:39 +00:00
tcl Fix gcc -Waddress warning in variables examples 2013-10-18 06:53:02 +01:00
test-suite Don't accept strings too long to fit in char[N] with trailing NUL. 2013-12-23 21:13:25 +00:00
xml XML example makefiles tweaks for consistency with other languages 2013-04-19 22:47:29 +01:00
index.html remove final vestiges of gifplot example 2010-02-28 00:16:39 +00:00
Makefile.in Use RUNME consistently in examples makefile 2013-12-20 18:52:19 +00:00
README remove final vestiges of gifplot example 2010-02-28 00:16:39 +00:00

SWIG Examples

The "perl5", "python", "tcl", "guile", "java", "mzscheme", "ruby", and
"chicken" directories 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.

The Examples directory is currently quite incomplete because it
is being reorganized.  A more complete set of examples can be found
in the SWIG1.1p5 distribution (most of which should still work with
SWIG1.3).

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 concering 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.