Use the system angle brackets for %include

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

Lib/allkw.swg

@@ -16,16 +16,16 @@
   
 */
 
-%include "chicken/chickenkw.swg"
-%include "csharp/csharpkw.swg"
-%include "java/javakw.swg"
-%include "php4/php4kw.swg"
-%include "pike/pikekw.swg"
-%include "python/pythonkw.swg"
-%include "ocaml/ocamlkw.swg"
-%include "ruby/rubykw.swg"
-%include "tcl/tclkw.swg"
-%include "perl5/perlkw.swg"
+%include <chicken/chickenkw.swg>
+%include <csharp/csharpkw.swg>
+%include <java/javakw.swg>
+%include <php4/php4kw.swg>
+%include <pike/pikekw.swg>
+%include <python/pythonkw.swg>
+%include <ocaml/ocamlkw.swg>
+%include <ruby/rubykw.swg>
+%include <tcl/tclkw.swg>
+%include <perl5/perlkw.swg>
 
 
 #endif //__Lib_allkw_swg__

Lib/chicken/chicken.swg

@@ -7,7 +7,7 @@
 /* chicken.h has to appear first. */
 
 %insert(runtime) %{
-#include "chicken.h"
+#include <chicken.h>
 %}
 
 %insert(runtime) "swigrun.swg";            // Common C API type-checking code
@@ -695,7 +695,7 @@ $result = C_SCHEME_UNDEFINED;
 
 #endif
 /* Warnings for certain CHICKEN keywords */
-%include "chickenkw.swg"
+%include <chickenkw.swg>
 
 /* TinyCLOS <--> Low-level CHICKEN */
 

Lib/chicken/typemaps.i

@@ -53,12 +53,12 @@ To use these, suppose you had a C function like this :
 
 You could wrap it with SWIG as follows :
         
-        %include typemaps.i
+        %include <typemaps.i>
         double fadd(double *INPUT, double *INPUT);
 
 or you can use the %apply directive :
 
-        %include typemaps.i
+        %include <typemaps.i>
         %apply double *INPUT { double *a, double *b };
         double fadd(double *a, double *b);
 
@@ -96,12 +96,12 @@ returns the integer part in one of its parameters).K:
 
 You could wrap it with SWIG as follows :
 
-        %include typemaps.i
+        %include <typemaps.i>
         double modf(double x, double *OUTPUT);
 
 or you can use the %apply directive :
 
-        %include typemaps.i
+        %include <typemaps.i>
         %apply double *OUTPUT { double *ip };
         double modf(double x, double *ip);
 
@@ -208,18 +208,18 @@ For example, suppose you were trying to wrap the following function :
 
 You could wrap it with SWIG as follows :
 
-        %include typemaps.i
+        %include <typemaps.i>
         void neg(double *INOUT);
 
 or you can use the %apply directive :
 
-        %include typemaps.i
+        %include <typemaps.i>
         %apply double *INOUT { double *x };
         void neg(double *x);
 
 As well, you can wrap variables with :
 
-        %include typemaps.i
+        %include <typemaps.i>
         %apply double *INOUT { double *y };
         extern double *y;
 

Lib/constraints.i

@@ -9,7 +9,7 @@
 
 #ifdef AUTODOC
 %text %{
-%include constraints.i
+%include <constraints.i>
 
 This library provides support for applying constraints to function
 arguments.  Using a constraint, you can restrict arguments to be
@@ -64,7 +64,7 @@ If you have used typedef to change type-names, you can also do this :
 %}
 #endif
 
-%include exception.i
+%include <exception.i>
 
 #ifdef SWIGCSHARP
 // Required attribute for C# exception handling

Lib/csharp/csharp.swg

@@ -4,7 +4,7 @@
  * CSharp typemaps
  * ----------------------------------------------------------------------------- */
 
-%include "csharphead.swg"
+%include <csharphead.swg>
 
 /* The ctype, imtype and cstype typemaps work together and so there should be one of each. 
  * The ctype typemap contains the PInvoke type used in the PInvoke (C/C++) code. 
@@ -640,10 +640,10 @@ using System.Runtime.InteropServices;
 %apply unsigned long { size_t };
 
 /* csharp keywords */
-%include "csharpkw.swg"
+%include <csharpkw.swg>
 
 // Default enum handling
-%include "enums.swg"
+%include <enums.swg>
 
 /*
 // Alternative char * typemaps.

Lib/csharp/std_pair.i

@@ -5,8 +5,8 @@
 //
 // Common implementation
 
-%include std_common.i
-%include exception.i
+%include <std_common.i>
+%include <exception.i>
 
 // ------------------------------------------------------------------------
 // std::pair

Lib/csharp/std_vector.i

@@ -358,6 +358,6 @@ SWIG_STD_VECTOR_SPECIALIZE(long, long long)
 SWIG_STD_VECTOR_SPECIALIZE(ulong, unsigned long long)
 SWIG_STD_VECTOR_SPECIALIZE(float, float)
 SWIG_STD_VECTOR_SPECIALIZE(double, double)
-SWIG_STD_VECTOR_SPECIALIZE(string, std::string) // also requires a %include "std_string.i"
+SWIG_STD_VECTOR_SPECIALIZE(string, std::string) // also requires a %include <std_string.i>
 
 

Lib/csharp/typemaps.i

@@ -43,12 +43,12 @@ To use these, suppose you had a C function like this :
 
 You could wrap it with SWIG as follows :
         
-        %include "typemaps.i"
+        %include <typemaps.i>
         double fadd(double *INPUT, double *INPUT);
 
 or you can use the %apply directive :
 
-        %include "typemaps.i"
+        %include <typemaps.i>
         %apply double *INPUT { double *a, double *b };
         double fadd(double *a, double *b);
 
@@ -121,12 +121,12 @@ returns the integer part in one of its parameters):
 
 You could wrap it with SWIG as follows :
 
-        %include "typemaps.i"
+        %include <typemaps.i>
         double modf(double x, double *OUTPUT);
 
 or you can use the %apply directive :
 
-        %include "typemaps.i"
+        %include <typemaps.i>
         %apply double *OUTPUT { double *ip };
         double modf(double x, double *ip);
 
@@ -201,12 +201,12 @@ For example, suppose you were trying to wrap the following function :
 
 You could wrap it with SWIG as follows :
 
-        %include "typemaps.i"
+        %include <typemaps.i>
         void neg(double *INOUT);
 
 or you can use the %apply directive :
 
-        %include "typemaps.i"
+        %include <typemaps.i>
         %apply double *INOUT { double *x };
         void neg(double *x);
 

Lib/guile/guile.i

@@ -26,4 +26,4 @@
 
 #define GUILE_APPEND_RESULT SWIG_APPEND_VALUE
 
-%include "typemaps.i"
+%include <typemaps.i>

Lib/guile/guile_gh.swg

@@ -7,7 +7,7 @@
 
 %runtime "swigrun.swg"
 %runtime "guile_gh_run.swg"
-%include "guile.i"
+%include <guile.i>
 
 %runtime %{
 

Lib/guile/guile_scm.swg

@@ -8,8 +8,8 @@
 %runtime "swigrun.swg"       // Common C API type-checking code
 
 %runtime "guile_scm_run.swg"
-%include "ghinterface.i"
-%include "guile.i"
+%include <ghinterface.i>
+%include <guile.i>
 
 %runtime %{
 

Lib/guile/std_pair.i

@@ -5,8 +5,8 @@
 //
 // Guile implementation
 
-%include std_common.i
-%include exception.i
+%include <std_common.i>
+%include <exception.i>
 
 // ------------------------------------------------------------------------
 // std::pair

Lib/guile/std_string.i

@@ -12,7 +12,7 @@
 // However, I think I'll wait until someone asks for it...
 // ------------------------------------------------------------------------
 
-%include exception.i
+%include <exception.i>
 
 %{
 #include <string>

Lib/java/arrays_java.i

@@ -7,7 +7,7 @@
    Example usage:
    Wrapping:
 
-     %include "arrays_java.i"
+     %include <arrays_java.i>
      %inline %{
          short FiddleSticks[3];
      %}

Lib/java/java.swg

@@ -5,7 +5,7 @@
  * ----------------------------------------------------------------------------- */
 
 
-%include "javahead.swg"
+%include <javahead.swg>
 
 /* The jni, jtype and jstype typemaps work together and so there should be one of each. 
  * The jni typemap contains the JNI type used in the JNI (C/C++) code. 
@@ -1192,8 +1192,8 @@ SWIG_PROXY_CONSTRUCTOR(true, true, SWIGTYPE)
 %apply unsigned long { size_t };
 
 /* java keywords */
-%include "javakw.swg"
+%include <javakw.swg>
 
 // Default enum handling
-%include "enumtypesafe.swg"
+%include <enumtypesafe.swg>
 

Lib/java/std_pair.i

@@ -5,8 +5,8 @@
 //
 // Common implementation
 
-%include std_common.i
-%include exception.i
+%include <std_common.i>
+%include <exception.i>
 
 // ------------------------------------------------------------------------
 // std::pair

Lib/java/typemaps.i

@@ -44,12 +44,12 @@ To use these, suppose you had a C function like this :
 
 You could wrap it with SWIG as follows :
         
-        %include "typemaps.i"
+        %include <typemaps.i>
         double fadd(double *INPUT, double *INPUT);
 
 or you can use the %apply directive :
 
-        %include "typemaps.i"
+        %include <typemaps.i>
         %apply double *INPUT { double *a, double *b };
         double fadd(double *a, double *b);
 
@@ -57,7 +57,7 @@ In Java you could then use it like this:
         double answer = modulename.fadd(10.0, 20.0);
 
 There are no char *INPUT typemaps, however you can apply the signed char * typemaps instead:
-        %include "typemaps.i"
+        %include <typemaps.i>
         %apply signed char *INPUT {char *input};
         void f(char *input);
 */
@@ -174,12 +174,12 @@ returns the integer part in one of its parameters):
 
 You could wrap it with SWIG as follows :
 
-        %include "typemaps.i"
+        %include <typemaps.i>
         double modf(double x, double *OUTPUT);
 
 or you can use the %apply directive :
 
-        %include "typemaps.i"
+        %include <typemaps.i>
         %apply double *OUTPUT { double *ip };
         double modf(double x, double *ip);
 
@@ -190,7 +190,7 @@ value in the single element array. In Java you would use it like this:
     double fraction = modulename.modf(5.0,ptr);
 
 There are no char *OUTPUT typemaps, however you can apply the signed char * typemaps instead:
-        %include "typemaps.i"
+        %include <typemaps.i>
         %apply signed char *OUTPUT {char *output};
         void f(char *output);
 */
@@ -310,12 +310,12 @@ For example, suppose you were trying to wrap the following function :
 
 You could wrap it with SWIG as follows :
 
-        %include "typemaps.i"
+        %include <typemaps.i>
         void neg(double *INOUT);
 
 or you can use the %apply directive :
 
-        %include "typemaps.i"
+        %include <typemaps.i>
         %apply double *INOUT { double *x };
         void neg(double *x);
 
@@ -332,7 +332,7 @@ languages in that other languages will return the output value as part
 of the function return value. This difference is due to Java being a typed language.
 
 There are no char *INOUT typemaps, however you can apply the signed char * typemaps instead:
-        %include "typemaps.i"
+        %include <typemaps.i>
         %apply signed char *INOUT {char *inout};
         void f(char *inout);
 */

Lib/lua/std_except.i

@@ -5,7 +5,7 @@
 %{
 #include <stdexcept>
 %}
-%include "exception.i"
+%include <exception.i>
 
 %typemap(throws) std::out_of_range %{
 SWIG_exception(SWIG_IndexError, $1.what()); %}

Lib/modula3/modula3.swg

@@ -4,7 +4,7 @@
  * Modula3 typemaps
  * ----------------------------------------------------------------------------- */
 
-%include "modula3head.swg"
+%include <modula3head.swg>
 
 /* The ctype, m3rawtype and m3wraptype typemaps work together and so there should be one of each. 
  * The ctype typemap contains the C type used in the signature of C wrappers for C++ functions. 

Lib/mzscheme/mzscheme.swg

@@ -19,7 +19,7 @@
 #define SCM_VALIDATE_LIST(argnum, value) (void)0
 
 /* Read in standard typemaps. */
-%include "typemaps.i"
+%include <typemaps.i>
 
 %insert(init) "swiginit.swg"