[Zlib-devel] zlib 1.2.4 released!

[William A. Rowe Jr.]

On 3/17/2010 11:18 AM, John Bowler wrote:
> 
> Zlib does *not* do this, so it's ok.  Libpng (as a counter example) *does* do this (app allocates (FILE), libpng uses it), so it is not ok.  It's an option to a libpng build (PNG_NO_STDIO) to remove the problem API.

As noted, gzdopen() does violate this.  We should be alert for others and
summarize them all.

> What I'm saying, though, is that zlib1 was released with a link to a particular CRT (MSVCRT) and it should not change that link.  If it doesn't change it a *user* upgrade of zlib1 doesn't change the libraries in the running app.  If it does change a *user* upgrade won't stop the app working, but it will result in an app with two CRTs where before there was only one.

This is a great assessment, John, great observation!