On Tue, 2005-09-20 at 15:11 -0400, Jonathan Blandford wrote:
I'm glad to hear that giflib has an active maintainer now.
Replacing
libungif with a maintained module makes a lot of sense. However,
looking at my distribution, it doesn't look like a whole lot of software
actually uses this library. This is a pity, as it's better to have just
one image loader available instead of multiple, especially when the
inevitable security errata happens.
True -- I've actually been wondering when everyone would switch to libgd
and giflib would die :-)
When we did the gif loaders for gdk-pixbuf, we looked at using
libungif.
However, it didn't support two vital features -- incremental loading and
sane threading support. I imagine that we could switch away from our
current code to libgif if those features appeared. Are you doing new
development on it? Is this in your roadmap at all?
I've just been merging bugfixes and trying to clean up the code. The
code is very old, only slightly less crufty than when I first looked at
it, and was first written with DOS in mind (I'm fixing a problem right
now in which int's were considered 16 bit so a long was used instead to
guarantee a 32 bit value... which breaks with 64bit longs.)
I could start doing new development to get threading and incremental
loading working, but knowing what the present code is like, I'm not sure
gdk-pixbuf would be more reliable for having switched.
-Toshio