update to use proxy terminology

git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk/SWIG@9177 626c5289-ae23-0410-ae9c-e8d60b6d4f22

Examples/test-suite/java/cpp_typedef_runme.java

@@ -1,5 +1,5 @@
 
-// This is the cpp_typedef runtime testcase. It checks that shadow classes are
+// This is the cpp_typedef runtime testcase. It checks that proxy classes are
 // generated for typedef'd types.
 
 import cpp_typedef.*;

Examples/test-suite/java/template_classes_runme.java

@@ -1,6 +1,6 @@
 
 // This is the template_classes runtime testcase. It checks that SWIG handles a templated 
-// class used by another templated class, in particular that the shadow classes can be used.
+// class used by another templated class, in particular that the proxy classes can be used.
 
 import template_classes.*;
 

Examples/test-suite/kind.i

@@ -1,6 +1,6 @@
 /* 
  * This interface file tests whether the language modules handle the kind when declared 
- * with the function/member name, especially when used with shadow classes.
+ * with the function/member name, especially when used with proxy classes.
 */
 
 %module kind

Examples/test-suite/r/double_delete_runme.R

@@ -1,4 +1,4 @@
-# This file illustrates the shadow-class C++ interface generated
+# This file illustrates the proxy class C++ interface generated
 # by SWIG.
 
 dyn.load('double_delete_wrap.so')
@@ -9,4 +9,4 @@ cacheMetaData(1)
 
 f <- Foo(2.0)
 delete(f);
-delete(f);
+delete(f);

Lib/python/defarg.swg

@@ -1,11 +1,11 @@
 /* This file defines an internal function for processing default arguments
-   with shadow classes.
+   with proxy classes.
 
-   There seems to be no straightforward way to write a shadow functions
+   There seems to be no straightforward way to write proxy functions
    involving default arguments. For example :
 
              def foo(arg1,arg2,*args):
-                     shadowc.foo(arg1,arg2,args)
+                     proxyc.foo(arg1,arg2,args)
 
    This fails because args is now a tuple and SWIG doesn't know what to
    do with it.
@@ -13,7 +13,7 @@
    This file allows a different approach :
 
             def foo(arg1,arg2,*args):
-                    shadowc.__call_defarg(shadowc.foo,(arg1,arg2,)+args)
+                    proxyc.__call_defarg(proxyc.foo,(arg1,arg2,)+args)
 
    Basically, we form a new tuple from the object, call this special
    __call_defarg method and it passes control to the real wrapper function.