[Zlib-devel] Explicit link to libc

[Enrico Weigelt]

* Mark Adler <madler at alumni.caltech.edu> schrieb:

Hi,

> > * newer versions may extend the existing interface, but NEVER
> >  break the existing one (so old apps always fit the new lib)
> 
> I agree.  This is why supporting 64-bit file offsets in 
> Windows will require some thought.

simple: add new functions.

> The Large File Summit had this same constraint.  Their solution 
> was to retain the old functions for linking, provide new types 
> and functions for 64-bit offsets using name64, and if requested 
> via a #define, redefine the old names to point to the new name64's.  

The last step (redirecting old funcs to 64bit ones) is crap. 
It changes semantics. And it doesnt bring any real benefit:
Code that shoudl benefit from larger offsets has to be aware of 
that fact, thus explicitly coping with larger types.

> This allows compiling new programs or recompiling old programs 
> to use 64-bit offsets with no fuss, but also avoids breaking 
> old programs linking to a dynamic library.

Thats misleading. The fact that (most) apps compile fine this
way, you're in great danger of hidden type mismatches.
 

cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
 	http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
	http://patches.metux.de/
---------------------------------------------------------------------