From: David G. <dge...@gm...> - 2012-07-10 14:59:29
|
SWIG Aficionados, I modified the SWIG 2.0.7 release source code to enable perl5 director support for a project I am working on. I based my implementation off a 2004 post by sfandino at: http://sourceforge.net/tracker/?func=detail&atid=301645&aid=914091&group_id=1645 Many changes were required from the original submission, but the posted patch helped out immensely and provided a really good starting point considering this is my first time playing around with SWIG. My modifications so far have been sufficient to enable multiple director classes which wrap a multi-threaded library without core dumps, odd behavior, or any sizable explosions. I am currently walking through the test-suite regression tests before I submit a patch to this email list, but have working code that completely satisfies my project needs. On the topic of submitting a patch, could anyone suggest or point me to an example of how best to make a code submission such as this or a list of steps that are required before the code change is accepted? ...I expect this info is in a FAQ or an archive message that I either cannot find or glossed over... Also, my code formatting differs from what is used throughout most of SWIG. Are there any automatic formatters (indent, .emacs file, etc.) or guidelines that you use to keep the code format consistent? Thanks! -Dave |