Keeping the API compatible is not really possible if the goal is to have multiple instances of PicoSAT co-exist in the same process, which actually was a long requested feature by many users. So I can not really go back to the old API. The only thing I can image is to add a compile time option which say 'PICOSAT_NON_REENTRANT', which if defined would use the old API. Still this would not allow binary compatability, only source compatability and then you could just recompile the new system using the new API anyhow ...
Armin On Tue, Dec 18, 2012 at 5:09 PM, Reinhard Tartler <siret...@tauware.de> wrote: > Package: picosat > Severity: important > > Dear picosat maintainers, > > I'm the author of a tool that links against picosat. I found that the > latest version of Picosat did change the API in an incompatible way. > This breaks the compilation of my applications. The problem is that if I > update to the new API, the compilation will break against older version > of picosat, which is widely deployed. I cannot require all my users to > update picosat at once, so I need to allow the successful compilation > against both the new and old API. > > Unfortunately, the file picosat.h header file does not indicate any > version string, so that implementing this becomes unnecessary hard. > > From what I understand from the README, this API change is necessary > because PicoSAT has become reentrant. This is great, but that feature > could have also been introduced with keeping API compatibility. > > Would it be possible to restore the API to picosat version 936, and > design the new API in a way that does not conflict? That would be much > appreciated. > > > Thanks for your consideration. > Reinhard > > -- > Gruesse/greetings, > Reinhard Tartler, KeyID 945348A4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
