summaryrefslogtreecommitdiff
path: root/CHANGES.current
diff options
context:
space:
mode:
authorWilliam S Fulton <wsf@fultondesigns.co.uk>2016-05-24 07:33:25 +0100
committerWilliam S Fulton <wsf@fultondesigns.co.uk>2016-05-24 19:09:17 +0100
commit763827c2e1fffd34e871c66d5d4c9e492c1cecec (patch)
tree3d74cca8c8db439211445c19916cb209f3f5651c /CHANGES.current
parentdc1fad3f9b591976a55a0987443b1de3dedccf0c (diff)
downloadswig-763827c2e1fffd34e871c66d5d4c9e492c1cecec.tar.gz
Ruby opaque pointer handling regression fix
This bug was introduced in swig-3.0.8 in #146252 adding shared_ptr support. An ObjectPreviouslyDeleted error was incorrectly thrown when the pointer was used as a parameter after being set to zero via a call to 'DATA_PTR(self) = 0'. It isn't clear to me which approach is better in this corner case, so I've gone for backwards compatibility and restored the old behaviour. Closes #602
Diffstat (limited to 'CHANGES.current')
-rw-r--r--CHANGES.current6
1 files changed, 6 insertions, 0 deletions
diff --git a/CHANGES.current b/CHANGES.current
index 6e347a7af..f754e96bd 100644
--- a/CHANGES.current
+++ b/CHANGES.current
@@ -5,6 +5,12 @@ See the RELEASENOTES file for a summary of changes in each release.
Version 3.0.9 (in progress)
===========================
+2016-05-23: wsfulton
+ [Ruby] Fix #602 - Error handling regression of opaque pointers introduced
+ in swig-3.0.8 when C functions explicitly reset a pointer using 'DATA_PTR(self) = 0'.
+ An ObjectPreviouslyDeleted error was incorrectly thrown when the pointer was used
+ as a parameter.
+
2016-05-17: tamuratak
[Ruby] Patch #651 - Correct overloaded function error message when function is
using %newobject.