<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jan 20, 2013 at 5:30 PM, Ben Morgan <span dir="ltr"><<a href="mailto:benpmorgan@gmail.com" target="_blank">benpmorgan@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Greg,<br><br><div class="gmail_quote"><div class="im">On Mon, Jan 21, 2013 at 6:28 AM, Greg Hellings <span dir="ltr"><<a href="mailto:greg.hellings@gmail.com" target="_blank">greg.hellings@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><br><div class="gmail_extra"><div><br></div><div class="gmail_quote"><br><div>SWIG bindings now up-to-date.</div><div>
<br></div><div>Bindings users, please holler if I removed things overzealously.</div><span><font color="#888888"><div><br></div></font></span></div></div></div></blockquote></div><div>I haven't tried it, but I believe that this will break BPBible for example.<br>
<br>As the bindings are part of SWORD, I believe it makes sense to mirror the deprecations in the bindings somehow if possible, rather than ignoring the deprecated definitions. <br>I know that's what e.g. wxPython does, but I'm not sure how it does it.<br>
</div></div></blockquote><div><br></div><div style>I can't see any way of marking the methods as deprecated using SWIG. A Google search has turned up no such evidence that it is even possible. While I would like to mark them as deprecated, I think it is more proper for there to be no such warnings coming from building the engine. I think it would just smack as an issue with building if the engine produced warnings that it uses its own deprecation warnings!</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote"><div>
</div><div> <br>Doing this will make it easier to support both SWORD 1.6 and SVN, which I think is desirable until a couple of versions down the road.<br></div></div></blockquote><div><br></div><div style>Supporting both is not something that either BibleTime or Xiphos is able to do at this point, either. In BT we maintain a separate branch for compatibility with SWORD while in Xiphos we simply can't make a new release until the engine releases. BPBible will probably need to take a similar path.</div>
<div style><br></div><div style>Part of cleaning up warnings from building are to allow the bindings to make it into distros. I've cleaned them up enough since 1.6.2 that hopefully this release will see at least Dmitrijs and whoever is our Fedora maintainer at this point able to build the bindings and include them in the distro which ought to allow BPBible to be packaged as well. Previously at least Debian was choking on the bindings failing to build due to warnings and -Werror flags.</div>
<div style><br></div><div style>In short, I'd rather keep these out unless there's a way to suppress the compile warnings and mark them as deprecated in the SWIG output. If you find evidence of that possibility, please let me know.</div>
<div style><br></div><div style>--Greg</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote"><div><br clear="all">God Bless,<br>Ben<br>
-------------------------------------------------------------<br>
<div>
<div>For I have no pleasure in the death of anyone, <br>declares the Lord <span style="font-variant:small-caps">God</span>; so turn, and live.”<br>Ezekiel 18:32 (ESV)</div>
</div>
</div></div>
<br>_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br></blockquote></div><br></div></div>