df899cfef1
* fflexo-javalist: Java std::vector minor improvement Fix Java container tests for change in vector constructor declaration Add in missing Java std::list listIterator index range checking Minor correction in C# std::list doNextIndex Add missing typedefs to Java std::vector Consistent destructor declarations Remove Java std::list::max_size Java std::list std::vector - test addAll and subList Handle length_error exceptions in Java std::vector::reserve Remove Java std::list::assign Additional add/remove methods added to Java std::list wrappers More efficient add implementation for Java std::list Java std::vector std::list: add missing exception handling Java std::vector std::list enhancements Modify std::list declarations to match the C++ standard Fix removing elements from std::list Java wrapper Improve Java std::list std::vector runtime tests and wrap std::list::clear Wrap std::list::empty as isEmpty in Java javabase typemap improvement for std::list Java std::list - fully qualifiy Java class name to avoid potential name ambiguity cosmetics Remove redundant code Java std::list rework to be consistent with std::vector wrappers li_std_list testcase not working for most languages re-enabled li_std_list test Switched from autobox to jboxtype per #842 Document autobox.i Made the conversion from long->int for size_type mapping onto Java interfaces cleaner. Be consistent in semantics of %extend on std::list::iterator Comment on consideration of making iterator non-static. Java style fix: iterator->Iterator Moving iterator functionality into nested Java class now. Removed typedef from li_std_list test as it's not expected to work properly in templated code Added a best case workaround for std::list::size_type vs jint problem. There's a bit of commentry added around it too for clarity. Drop non-const reference from autobox typemap macro to be consistent. just use a forward declaration for C++ iterator types to fix enum errors Added enum to li_std_list tests Added li_std_list to the Java test-suit makefile added more comments in a few places Base _runme.java for li_std_list off li_std_vector_runme.java Expose more types from li_std_list.i Don't expose sort() to avoid adding dependencies on all std::list users Target each method specificly for setting modifiers Don't expose remove() method from std::list to avoid confusing it with Java's remove() in List - added std_list.i implemenatation that extends Java's AbstractSequentialList base class - added autobox.i that provides supporting typemaps for generics in containers |
||
|---|---|---|
| .. | ||
| android | ||
| chicken | ||
| contract | ||
| csharp | ||
| d | ||
| go | ||
| guile | ||
| java | ||
| javascript | ||
| lua | ||
| modula3 | ||
| mzscheme | ||
| ocaml | ||
| octave | ||
| perl5 | ||
| php | ||
| php5 | ||
| pike | ||
| python | ||
| r | ||
| ruby | ||
| s-exp | ||
| scilab | ||
| tcl | ||
| test-suite | ||
| xml | ||
| index.html | ||
| Makefile.in | ||
| 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.