[Zlib-devel] crc32 big/little endian

[Mark Adler]

On Apr 21, 2010, at 10:34 AM, John Bowler wrote:
> My own opinion is that the default build should be small and that it should be the relatively smaller number of high-end platform builders (who have more time and more money) who should be turning on options.  But then the high end platform builders tend to be a lot louder too, so it may be less suffering for *you* just to put all the fat code in by default.

I guess what I have assumed, possibly with only cursory consideration, is that the default settings of zlib should be to optimize speed, not space.  The speed clamorers seem much louder than the space clamorers.  However I am open to discussion.

(And yes of course, less suffering for me is certainly my prime consideration!)

My assumption was the embedded developers are much more likely to rip into the zlib source and squeeze out exactly what they need and no more, whereas the big system developers just want to use zlib as is, and want it to be fast with no concern for memory usage at the scale of zlib.

> It would be nice to know, reliably, at every release, how to get rid of it ;-)


If space is really more important than speed, then I could come up with a space-optimized version of zlib based on puff, a scaled-down deflate, and the short versions of adler32 and crc32, and leave out the rest of the stuff.

Mark