Subject: zlib #ifdef in headers
To: None <,>
From: Jun-ichiro itojun Hagino <>
List: tech-userlevel
Date: 08/31/2000 17:52:08
	(To: field is set to zlib maintainer - see doc/3RDPARTY)
	there are tons of #ifdef in zlib headers.  zlib headers will be put
	into /usr/include, and will be used by userland applications.
	those #ifdef can make libz.a and userland build pick a different idea
	about variable types, and struct sizes, and can lead to hard-to-track
	i'm thinking of removing unnecessary #ifdef crufts from those headers,
	or disabling them by wrapping those with #ifdef __NetBSD__ (or
	#ifndef __NetBSD__).

	is it acceptable from code synchronization (with zlib master
	distribution) standpoint?  or am I doing something wrong?