From: Bob H. <bh...@co...> - 2010-05-21 13:38:12
|
Any heads-up about how traumatic the switch to SWIG 2.0 will be for entrenched users of 1.3.x? I've spent the better part of the past six months integrating Python 2.6.x into our unreleased product, and I'm wanting to gauge how much more effort will be involved in switching to the new version. I can't afford to throw too much of a monkey wrench into the current works. |
From: William S F. <ws...@fu...> - 2010-05-25 18:52:40
|
Bob Hood wrote: > Any heads-up about how traumatic the switch to SWIG 2.0 will be for > entrenched users of 1.3.x? I've spent the better part of the past six > months integrating Python 2.6.x into our unreleased product, and I'm > wanting to gauge how much more effort will be involved in switching to > the new version. I can't afford to throw too much of a monkey wrench > into the current works. > It should be as easy/hard (take your pick) as it normally is to upgrade. There are some subtle changes, maybe slightly more than usual, but it really depends on how complex your interface file is. The current list of changes can be viewed here: http://swig.svn.sourceforge.net/viewvc/swig/trunk/CHANGES.current Known potential incompatibilities are marked. William |
From: Bob H. <bh...@co...> - 2010-05-25 19:19:40
|
On 5/25/2010 12:52 PM, William S Fulton wrote: > Bob Hood wrote: >> Any heads-up about how traumatic the switch to SWIG 2.0 will be for >> entrenched users of 1.3.x? I've spent the better part of the past six >> months integrating Python 2.6.x into our unreleased product, and I'm >> wanting to gauge how much more effort will be involved in switching to >> the new version. I can't afford to throw too much of a monkey wrench >> into the current works. >> > It should be as easy/hard (take your pick) as it normally is to > upgrade. There are some subtle changes, maybe slightly more than > usual, but it really depends on how complex your interface file is. > The current list of changes can be viewed here: > > http://swig.svn.sourceforge.net/viewvc/swig/trunk/CHANGES.current > > Known potential incompatibilities are marked. Thanks a bunch, William! |