From 78c4626ae62670924e4a5ecbe3dd9c70e38d3d9e Mon Sep 17 00:00:00 2001
From: William S Fulton <wsf@fultondesigns.co.uk>
Date: Sun, 28 Nov 2004 19:23:07 +0000
Subject: [PATCH] *** empty log message ***

git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@6788 626c5289-ae23-0410-ae9c-e8d60b6d4f22
---
 SWIG/CHANGES.current | 50 ++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 50 insertions(+)

diff --git a/SWIG/CHANGES.current b/SWIG/CHANGES.current
index ad231dbfb..8316d5729 100644
--- a/SWIG/CHANGES.current
+++ b/SWIG/CHANGES.current
@@ -1,6 +1,56 @@
 Version 1.3.23 (working version)
 =================================
 
+11/25/2004: wsfulton
+            const enum SWIGTYPE & typemaps added. These wrap const enum references
+            as if they were passed by value. Const enum references thus work the
+            same as const reference primitive types such as const double &, 
+            const int & etc. Typemaps added for Java, C#, Ruby, Tcl, Perl and Pike.
+
+11/25/2004: wsfulton
+            [Java, C#] New special variable: $*javaclassname, similar to $javaclassname
+            and $&javaclassname. The new one removes a pointer from the C type before
+            obtaining the Java class name. One or more of $javaclassname,
+            $&javaclassname or $*javaclassname may now appear in a typemap. Likewise for
+            C# using csclassname instead of javaclassname.
+
+11/25/2004: wsfulton
+            The last vestiges of enums being handled as integers removed from the
+            internals. The wrapper methods use the enum type rather than an int
+            now. The net result is added type safety for enums when handled as
+            pointers, references etc. Previously in situations such as a method
+            taking a pointer to an enum, a pointer to an int or a pointer to an
+            enum of some other type could inadvertantly be passed to the method.
+            This is now fixed as the descriptor for an enum is no longer based on
+            an int, but the enum type instead. Anonymous enums are still handled
+            as integers.
+
+            The consequence for scripting language users in correct usage of enums
+            should not be noticeable. There is no change for any of the languages
+            where enums are passed by value - most of the scripting languages will
+            still accept an integer for an enum value and the strongly typed
+            languages still use either typesafe enums, integers or proper enums
+            depending on what the user configures. For Java and C# users a change
+            in the typewrapper class name has occurred (for enum pointers,
+            references etc). For example:
+
+              enum Numbers { one=1, two };
+              enum Numbers* number();
+
+            In Java and C# this must now be coded as
+
+              SWIGTYPE_p_Numbers n = modulename.number();
+
+            rather than
+
+              SWIGTYPE_p_int n = modulename.number();
+
+            *** POTENTIAL INCOMPATIBILITY ***
+
+11/21/2004: wsfulton/mmatus
+            Added missing deprecated warning for %name and remove remaining %name
+            usage in the SWIG libraries.
+
 11/21/04: mmatus
 	    - [Python] Adding the PySwigObject to be used for carrying
 	      the instance C/C++ pointers. This is used instead of