Initial commit

winx64/bin/swig-3.0.12/Examples/go/reference/Makefile

@@ -0,0 +1,18 @@
+TOP        = ../..
+SWIGEXE    = $(TOP)/../swig
+SWIG_LIB_DIR = $(TOP)/../$(TOP_BUILDDIR_TO_TOP_SRCDIR)Lib
+CXXSRCS    = reference.cxx
+TARGET     = example
+INTERFACE  = example.i
+SWIGOPT    =
+
+check: build
+	$(MAKE) -f $(TOP)/Makefile SRCDIR='$(SRCDIR)' CXXSRCS='$(CXXSRCS)' TARGET='$(TARGET)' INTERFACE='$(INTERFACE)' go_run
+
+build:
+	$(MAKE) -f $(TOP)/Makefile SRCDIR='$(SRCDIR)' CXXSRCS='$(CXXSRCS)' \
+	SWIG_LIB_DIR='$(SWIG_LIB_DIR)' SWIGEXE='$(SWIGEXE)' \
+	SWIGOPT='$(SWIGOPT)' TARGET='$(TARGET)' INTERFACE='$(INTERFACE)' go_cpp
+
+clean:
+	$(MAKE) -f $(TOP)/Makefile SRCDIR='$(SRCDIR)' INTERFACE='$(INTERFACE)' go_clean

winx64/bin/swig-3.0.12/Examples/go/reference/example.h

@@ -0,0 +1,22 @@
+/* File : example.h */
+
+class Vector {
+private:
+  double x,y,z;
+public:
+  Vector() : x(0), y(0), z(0) { }
+  Vector(double x, double y, double z) : x(x), y(y), z(z) { }
+  friend Vector operator+(const Vector &a, const Vector &b);
+  char *print();
+};
+
+class VectorArray {
+private:
+  Vector *items;
+  int     maxsize;
+public:
+  VectorArray(int maxsize);
+  ~VectorArray();
+  Vector &operator[](int);
+  int size();
+};

winx64/bin/swig-3.0.12/Examples/go/reference/example.i

@@ -0,0 +1,42 @@
+/* File : example.i */
+
+/* This file has a few "typical" uses of C++ references. */
+
+%module example
+
+%{
+#include "example.h"
+%}
+
+class Vector {
+public:
+    Vector(double x, double y, double z);
+   ~Vector();
+    char *print();
+};
+
+/* This helper function calls an overloaded operator */
+%inline %{
+Vector addv(Vector &a, Vector &b) {
+  return a+b;
+}
+%}
+
+/* Wrapper around an array of vectors class */
+
+class VectorArray {
+public:
+  VectorArray(int maxsize);
+  ~VectorArray();
+  int size();
+
+  /* This wrapper provides an alternative to the [] operator */
+  %extend {
+    Vector &get(int index) {
+      return (*$self)[index];
+    }
+    void set(int index, Vector &a) {
+      (*$self)[index] = a;
+    }
+  }
+};

winx64/bin/swig-3.0.12/Examples/go/reference/index.html

@@ -0,0 +1,143 @@
+<html>
+<head>
+<title>SWIG:Examples:go:reference</title>
+</head>
+
+<body bgcolor="#ffffff">
+
+
+<tt>SWIG/Examples/go/reference/</tt>
+<hr>
+
+<H2>C++ Reference Handling</H2>
+
+<p>
+This example tests SWIG's handling of C++ references.  A reference in
+C++ is much like a pointer.  Go represents C++ classes as pointers
+which are stored in interface values.  Therefore, a reference to a
+class in C++ simply becomes an object of the class type in Go.  For
+types which are not classes, a reference in C++ is represented as a
+pointer in Go.
+
+<h2>Some examples</h2>
+
+References are most commonly used as function parameters.  For
+example, you might have a function like this:
+
+<blockquote>
+<pre>
+Vector addv(const Vector &amp;a, const Vector &amp;b) {
+   Vector result;
+   result.x = a.x + b.x;
+   result.y = a.y + b.y;
+   result.z = a.z + b.z;
+   return result;
+}
+</pre>
+</blockquote>
+
+In these cases, SWIG transforms everything into a pointer and creates
+a wrapper that looks like this in C++.
+
+<blockquote>
+<pre>
+Vector wrap_addv(Vector *a, Vector *b);
+</pre>
+</blockquote>
+
+or like this in Go:
+
+<blockquote>
+<pre>
+func Addv(arg1 Vector, arg2 Vector) Vector
+</pre>
+</blockquote>
+
+Occasionally, a reference is used as a return value of a function
+when the return result is to be used as an lvalue in an expression.
+The prototypical example is an operator like this:
+
+<blockquote>
+<pre>
+Vector &amp;operator[](int index);
+</pre>
+</blockquote>
+
+or a method:
+
+<blockquote>
+<pre>
+Vector &amp;get(int index);
+</pre>
+</blockquote>
+
+For functions returning references, a wrapper like this is created:
+
+<blockquote>
+<pre>
+Vector *wrap_Object_get(Object *self, int index) {
+    Vector &amp;result = self-&gt;get(index);
+    return &amp;result;
+}
+</pre>
+</blockquote>
+
+The following <a href="example.h">header file</a> contains some class
+definitions with some operators and use of references.
+
+<h2>SWIG Interface</h2>
+
+SWIG does NOT support overloaded operators so it can not directly
+build an interface to the classes in the above file.  However, a
+number of workarounds can be made.  For example, an overloaded
+operator can be stuck behind a function call such as the <tt>addv</tt>
+function above.  Array access can be handled with a pair of set/get
+functions like this:
+
+<blockquote>
+<pre>
+class VectorArray {
+public:
+ ...
+   %addmethods {
+    Vector &amp;get(int index) {
+      return (*self)[index];
+    }
+    void set(int index, Vector &amp;a) {
+      (*self)[index] = a;
+    }
+   }
+   ...
+}
+</pre>
+</blockquote>
+
+Click <a href="example.i">here</a> to see a SWIG interface file with
+these additions.
+
+<h2>Sample Go program</h2>
+
+Click <a href="runme.go">here</a> to see a Go program that manipulates
+some C++ references.
+
+<h2>Notes:</h2>
+
+<ul>
+<li>C++ references primarily provide notational convenience for C++
+source code.  However, Go only supports the 'x.a' notation so it
+doesn't much matter.
+
+<p>
+<li>When a program returns a reference, a pointer is returned.  Unlike
+return by value, memory is not allocated to hold the return result.
+
+<p>
+<li>SWIG has particular trouble handling various combinations of
+references and pointers.  This is side effect of an old parsing scheme
+and type representation that will be replaced in future versions.
+
+</ul>
+
+<hr>
+</body>
+</html>

winx64/bin/swig-3.0.12/Examples/go/reference/reference.cxx

@@ -0,0 +1,46 @@
+/* File : example.cxx */
+
+/* Deal with Microsoft's attempt at deprecating C standard runtime functions */
+#if !defined(SWIG_NO_CRT_SECURE_NO_DEPRECATE) && defined(_MSC_VER)
+# define _CRT_SECURE_NO_DEPRECATE
+#endif
+
+#include "example.h"
+#include <stdio.h>
+#include <stdlib.h>
+
+Vector operator+(const Vector &a, const Vector &b) {
+  Vector r;
+  r.x = a.x + b.x;
+  r.y = a.y + b.y;
+  r.z = a.z + b.z;
+  return r;
+}
+
+char *Vector::print() {
+  static char temp[512];
+  sprintf(temp,"Vector %p (%g,%g,%g)", (void *)this, x,y,z);
+  return temp;
+}
+
+VectorArray::VectorArray(int size) {
+  items = new Vector[size];
+  maxsize = size;
+}
+
+VectorArray::~VectorArray() {
+  delete [] items;
+}
+
+Vector &VectorArray::operator[](int index) {
+  if ((index < 0) || (index >= maxsize)) {
+    printf("Panic! Array index out of bounds.\n");
+    exit(1);
+  }
+  return items[index];
+}
+
+int VectorArray::size() {
+  return maxsize;
+}
+

winx64/bin/swig-3.0.12/Examples/go/reference/runme.go

@@ -0,0 +1,71 @@
+// This example illustrates the manipulation of C++ references in Java.
+
+package main
+
+import (
+	. "./example"
+	"fmt"
+)
+
+func main() {
+	fmt.Println("Creating some objects:")
+	a := NewVector(3, 4, 5)
+	b := NewVector(10, 11, 12)
+
+	fmt.Println("    Created ", a.Print())
+	fmt.Println("    Created ", b.Print())
+
+	// ----- Call an overloaded operator -----
+
+	// This calls the wrapper we placed around
+	//
+	//      operator+(const Vector &a, const Vector &)
+	//
+	// It returns a new allocated object.
+
+	fmt.Println("Adding a+b")
+	c := Addv(a, b)
+	fmt.Println("    a+b = " + c.Print())
+
+	// Because addv returns a reference, Addv will return a
+	// pointer allocated using Go's memory allocator.  That means
+	// that it will be freed by Go's garbage collector, and we can
+	// not use DeleteVector to release it.
+
+	c = nil
+
+	// ----- Create a vector array -----
+
+	fmt.Println("Creating an array of vectors")
+	va := NewVectorArray(10)
+	fmt.Println("    va = ", va)
+
+	// ----- Set some values in the array -----
+
+	// These operators copy the value of Vector a and Vector b to
+	// the vector array
+	va.Set(0, a)
+	va.Set(1, b)
+
+	va.Set(2, Addv(a, b))
+
+	// Get some values from the array
+
+	fmt.Println("Getting some array values")
+	for i := 0; i < 5; i++ {
+		fmt.Println("    va(", i, ") = ", va.Get(i).Print())
+	}
+
+	// Watch under resource meter to check on this
+	fmt.Println("Making sure we don't leak memory.")
+	for i := 0; i < 1000000; i++ {
+		c = va.Get(i % 10)
+	}
+
+	// ----- Clean up ----- This could be omitted. The garbage
+	// collector would then clean up for us.
+	fmt.Println("Cleaning up")
+	DeleteVectorArray(va)
+	DeleteVector(a)
+	DeleteVector(b)
+}