From owner-freebsd-arch@FreeBSD.ORG Sun Oct 17 04:44:59 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 49DA016A4CE; Sun, 17 Oct 2004 04:44:59 +0000 (GMT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [128.30.28.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id D341243D54; Sun, 17 Oct 2004 04:44:58 +0000 (GMT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id i9H4iuqw077076 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK CN=khavrinen.lcs.mit.edu issuer=SSL+20Client+20CA); Sun, 17 Oct 2004 00:44:57 -0400 (EDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.9/8.12.9/Submit) id i9H4iu1M077075; Sun, 17 Oct 2004 00:44:56 -0400 (EDT) (envelope-from wollman) Date: Sun, 17 Oct 2004 00:44:56 -0400 (EDT) From: Garrett Wollman Message-Id: <200410170444.i9H4iu1M077075@khavrinen.lcs.mit.edu> To: obrien@freebsd.org In-Reply-To: <20041017011608.GA6140@dragon.nuxi.com> References: <20041016174419.GA96297@dragon.nuxi.com> <20041016183202.GA76917@VARK.MIT.EDU> Organization: MIT Laboratory for Computer Science X-Spam-Score: -19.8 () IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES X-Scanned-By: MIMEDefang 2.37 cc: arch@freebsd.org Subject: Re: Proposal to restore traditional BSD behavior in . X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Oct 2004 04:44:59 -0000 In article <20041017011608.GA6140@dragon.nuxi.com> you write: >On Sat, Oct 16, 2004 at 02:32:02PM -0400, David Schultz wrote: >> On Sat, Oct 16, 2004, David O'Brien wrote: >> > I'd like to restore the traditional BSD behavior that >> > includes the content of in addition to the BSD bcmp, et. al. >> > We changed our between 4.x and 5.x and now that we're at >> > 5-STABLE I'm finding software that built fine on 4.x has an issue on 5.x. >> >> It has been this way for 2.5 years, and nobody has complained >> until now AFAIK. Therefore, it seems unlikely that there's enough >> affected unportable software out there to justify undoing the >> efforts at reducing namespace pollution now. >> >> Moreover, there's a *lot* of pollution in string.h, where as >> strings.h has very little. Polluting strings.h again increases >> the chances that portable applications that use strings.h will >> break due to naming conflicts. > > isn't POSIX. BZZZT! Wrong, but thanks for playing. See XBD6 page 331. However, it is an XSI header, and we don't claim to support XSI, so theoretically we can define anything we want in . I believe, however, that it has been a better policy to force-migrate users of the functions specified in the C standard to the header specified in the C standard. -GAWollman