From owner-freebsd-current Mon Nov 12 15: 8: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id B7B0337B416 for ; Mon, 12 Nov 2001 15:08:06 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id fACN7wa87802; Mon, 12 Nov 2001 18:07:58 -0500 (EST) (envelope-from wollman) Date: Mon, 12 Nov 2001 18:07:58 -0500 (EST) From: Garrett Wollman Message-Id: <200111122307.fACN7wa87802@khavrinen.lcs.mit.edu> To: Steve Kargl Cc: freebsd-current@FreeBSD.ORG Subject: namespace pollution with struct thread? In-Reply-To: <20011112140135.A42228@troutmask.apl.washington.edu> References: <20011112140135.A42228@troutmask.apl.washington.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG < said: > I WINE developer has suggested that this is namespace > pollution on the part of FreeBSD, but he hasn't given > any details to support what he means. Applications which include , or any other non-standard header file, should expect that any conceivable symbol might be used therein. FreeBSD makes no guarantees as to the namespace used by non-standard interfaces. (We don't want to be like certain other environments where every symbol that might conceivably be accessible to an application is obfuscated with multiple underscores.) -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message