[Zlib-devel] zlib 1.2.4 released!

[William A. Rowe Jr.]

On 3/20/2010 1:16 PM, Mark Adler wrote:
> On Mar 17, 2010, at 3:37 AM, Mark Brown wrote:
>> Windows DLL linking is different to Unix shared libraries since the link
>> is to a specific symbol in a specific DLL rather than to a symbol in any
>> old DLL the process happens to load, meaning that you can have multiple
>> copies of the runtime in one process without any upset so long as you
>> don't try to make the two copies talk to each other.
> 
> "Multiple copies of the runtime"?!  What evil genius at Microsoft came up with this fiendish way to make passing an *integer* file descriptor unsafe?  Truly amazing.

What is more fun is that -they learned this lesson once- ;-)  That was when they
finally came up with MSVCRT, the c runtime to end all runtimes, which would be
fixed for security bugs and kept in a common location.  Somehow they only managed
a few product cycles before falling back on errant ways.

> On Mar 19, 2010, at 1:35 AM, William A. Rowe Jr. wrote:
>> DLL_FAQ.txt, zlib.3.pdf, ChangeLog, and the revised README-WIN32.txt were added
>> and the zip file re-pgp-signed.
>> http://people.apache.org/~wrowe/zlib-1.2.4-win32-x86.zip [.asc]
> 
> Thank you!   Some comments ...
> 
> In the zconf.h distributed with the DLL, should the following line be edited for z_off_t to be defined properly?
> 
> #ifdef HAVE_UNISTD_H    /* may be set to #if 1 by ./configure */

off_t is learned from sys/types.h; unistd.h is alien to win32; it happens to be a long,
which is 32 bits on both x86 and x64 architectures.  Don't know the IA64 mapping offhand.
The z_off64_t will want to be an __int64, once we get that far.

> The README-WIN32.txt file has carriage returns, but the other text files do not.  Should they all have carriage returns?  Should none of them have carriage returns?  (I would prefer the latter so that I can edit them without having to think about maintaining carriage returns.  One of the files in the zlib 1.2.4 distribution was rejected by someone's system because it had a mix of lines with and without carriage returns that was a result of me editing that file.)

Actually all the text files [in the zip] have their carriage returns.  Please keep
the source file without CR/LF's as all the other files you track; Blessing these
when packaging for windows is absolutely trivial.  As a subversion user, I keep it
all as 'native' and just borrow the svn export --native-eol trick to do the 'other
platforms' package (e.g. just as simple to do LF's on win32 or CRLF's on unix).

>>From the README:
> 
> "Questions about zlib should be sent to <zlib-devel at zlib.net>."
> 
> The email there should be zlib at gzip.org .  Email to zlib-devel is only accepted from members of zlib-devel.

Fixed, rerolled with CR/LF's, same location; But the LF-only flavor of that
readme is attached for you to track with the project sources.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: README-WIN32.txt
URL: <http://madler.net/pipermail/zlib-devel_madler.net/attachments/20100320/ccfa8bdc/attachment.txt>