From 72c9fe5ba735db8494597c13535ca2ae52110e2f Mon Sep 17 00:00:00 2001
From: Marcelo Matus <mmatus@acms.arizona.edu>
Date: Mon, 29 Mar 2004 06:17:12 +0000
Subject: [PATCH] *** empty log message ***

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

diff --git a/CHANGES.current b/CHANGES.current
index cc5da6e9e..eae75327b 100644
--- a/CHANGES.current
+++ b/CHANGES.current
@@ -1,6 +1,36 @@
 Version 1.3.22 (in progress)
 ==================================
 
+03/21/2004: mmatus
+	    [Python] Makes the following 'var' cases more uniform:
+
+                std::string ga;
+ 
+                struct A {
+                  static std::string sa;
+                  std::string ma;
+                };
+
+
+            now the three variables (ga, sa, ma) can be assigned as:
+
+
+                  cvar.ga = "hello";
+                  A.sa = "hello";
+                  a.ma = "hello";
+
+            ie, now 'ma' will also use a std::string typemap 'in' if
+            defined, before it was only accepting a 'p_std_string'
+            pointer.  Note, however, that 'ma' will not use the
+            'varin/varout' typemaps (that probably could be more
+            natural), but it will pick up the 'in' typemap for const
+            std::string& (which is easier).
+
+	    The changes in cwrap.c and lang.cxx will probably fix the
+	    behaviour in other languages that do not overload the
+	    membervarHandler method "too much".
+ 
+            
 03/21/2004: mmatus
 	    [Python] Disabling the default instantiations like: