From owner-cvs-all@FreeBSD.ORG Wed May 28 00:21:31 2008 Return-Path: Delivered-To: cvs-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E26B5106566B; Wed, 28 May 2008 00:21:31 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from sippysoft.com (gk1.360sip.com [72.236.70.240]) by mx1.freebsd.org (Postfix) with ESMTP id AB2E28FC13; Wed, 28 May 2008 00:21:31 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from [192.168.0.40] ([204.244.149.125]) (authenticated bits=0) by sippysoft.com (8.13.8/8.13.8) with ESMTP id m4S0LSIm026607 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 27 May 2008 17:21:30 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Message-ID: <483CA584.3080001@FreeBSD.org> Date: Tue, 27 May 2008 17:21:24 -0700 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Erik Trulsson References: <200805272004.m4RK4SZt029194@repoman.freebsd.org> <483C7FF2.6000607@FreeBSD.org> <20080527234335.GA24995@owl.midgard.homeip.net> In-Reply-To: <20080527234335.GA24995@owl.midgard.homeip.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, Xin LI , cvs-all@FreeBSD.org Subject: Re: cvs commit: src/include string.h src/lib/libc/string Makefile.inc memchr.3 memrchr.c src/sys/sys param.h X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 May 2008 00:21:32 -0000 Erik Trulsson wrote: > On Tue, May 27, 2008 at 02:41:06PM -0700, Maxim Sobolev wrote: >> Xin LI wrote: >>> delphij 2008-05-27 20:04:27 UTC >>> >>> FreeBSD src repository >>> >>> Modified files: (Branch: RELENG_6) >>> include string.h >>> lib/libc/string Makefile.inc memchr.3 >>> sys/sys param.h >>> Added files: (Branch: RELENG_6) >>> lib/libc/string memrchr.c >>> Log: >>> MFC: Add memrchr(3). >> I think this is not very good idea to MFC that into stable releases 6.x >> and 7.x. The reason is that configure scripts for some packages might >> detect up this API and enable it. Which means that some binary-only >> packages build for say 6.4 won't work on 6.3 and down. AFAIK, both >> forward and backward compatibility is required (or at least desired?) >> for stable branches. > > No, it isn't. Backwards compatibility (in the sense that stuff that worked > on 6.x should still work on 6.x+1) is largely required unless there is > some very good reason to break compatibility (such very good reasons are > quite rare.) Which reasons are they specifically? I can't think of any. The memrchr() is not something mandated by the C90 and/or POSIX/SUS. Any software that is portable should be able to live without it. -Maxim