From owner-freebsd-current Mon Nov 12 16: 0:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 1219137B417 for ; Mon, 12 Nov 2001 16:00:31 -0800 (PST) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id PAA95492; Mon, 12 Nov 2001 15:50:17 -0800 (PST) Date: Mon, 12 Nov 2001 15:50:16 -0800 (PST) From: Julian Elischer To: Garrett Wollman Cc: Steve Kargl , freebsd-current@FreeBSD.ORG Subject: Re: namespace pollution with struct thread? In-Reply-To: <200111122307.fACN7wa87802@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On the other hand we might conceivably be able to stop the export from the kernel of this struct type. On Mon, 12 Nov 2001, Garrett Wollman wrote: > < 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message