Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#58 giflib has too many unnecessary API changes

v1.0_(example)
closed
nobody
None
1
2014-05-17
2014-05-16
Thomas Klausner
No

giflib changes their API too much for unnecessary reasons. Nearly every recent release has needed source changes in the applications using it.

The latest example is the 5.1.0 release. The CloseFile functions were extended with a second argument. It would have been easy to do this in a backwards-compatible way: Just add a new function that has the additional argument, let's say DGifCloseFileError, and make DGifCloseFile a wrapper like:

int
DGifCloseFile(GifFileType *GifFile)
{
return int DGifCloseFileError(GifFile, NULL);
}

I'm not expecting you to change this now, but please, please take more care of backwards compat in the future.

Discussion

  • The 4.x line of development is still maintained for those who require absolute backward compatibility. If you don't like the 5.x changes you can drop back to that.

    I have actually thought about the API changes carefully. Rather than explain my philosophy here I think I'll address the issues in a blog post at Armed & Dangerous. Probably tomorrow.

     
    • status: open --> closed