Thanks for looking into this so quickly and doing the digging in documentations. Your code works just fine for me.
I also patched my local swig copy – i.e. changed the macro in Lib\python\builtin.swg and swig now produces working code. What is the way to go to get this into the next release?
Andreas Schoenle, Dr.
Department of NanoBiophotonics
Max-Planck-Institute for Biophysical Chemistry D-37070 Gottingen, Germany
phone:+49 551 201 2611
fax:+49 551 201 2505
From: Christian Delbaere [mailto:email@example.com]
Sent: Saturday, June 22, 2013 10:04 PM
Subject: Re: [Swig-devel] Issue with python builtin mode and director classes
Thanks for the work you've done on this issue. I've updated the bug report with my findings. I've changed your solution slightly to eliminate a memory leak, but I think now we've got the right code. Can you check out the bug report and try it out? Let me know if it's working well for you and then we can create a patch for consideration in the next release.
Date: Thu, 20 Jun 2013 10:39:46 +0200
From: Andreas Sch?nle <firstname.lastname@example.org>
Subject: [Swig-devel] Issue with python builtin mode and director
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
we were running into what seems to be a bug concerning de-allocation of
extended director classes in builtin mode that had been previously
I have added a comment there, describing what little I could figure out.
Is this the way to go for issues on the sourceforge site?
I noticed that things have moved to GitHub - would it be better to move
the issue there linking back to the original issue on sourcforge?
Thanks and best regards,