Date: Thu, 25 Oct 2007 23:14:37 +0400 From: Andrey Chernov <ache@nagual.pp.ru> To: Scott Long <scottl@samsco.org> Cc: cvs-src@FreeBSD.ORG, src-committers@FreeBSD.ORG, d@delphij.net, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/lib/libc/locale utf8.c Message-ID: <20071025191437.GD16187@nagual.pp.ru> In-Reply-To: <4720EA15.40002@samsco.org> References: <200710150951.l9F9pUm7026506@repoman.freebsd.org> <4720B30F.4040903@samsco.org> <20071025151707.GA11398@nagual.pp.ru> <4720E0AF.1010004@samsco.org> <4720E904.2090704@delphij.net> <4720EA15.40002@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 25, 2007 at 01:10:13PM -0600, Scott Long wrote: >> Well, I think the problem is not exposing a new symbol by itself, but >> __mb_sb_limit is being used in _ctype.h, in a form of __inline >> functions. Therefore, the change will break new binaries running on >> older systems. Personally I think this is acceptable, but maybe we >> could have a better way to avoid this, because the binaries are no >> longer backward compatible (i.e. you may have trouble running a program >> compiled for 6.3-RELEASE on 6.2-RELEASE, if it uses locale bits). > > If this is true, then it directly violates the API/ABI compatability > guidelines that were developed and agreed to by the project in 2005. We define only backward compatibility, not forward one. Do you f.e. expect to run 7x binaries on 6x as is? At least compat7x required (if all syscall are the same). -- http://ache.pp.ru/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071025191437.GD16187>