From owner-svn-src-all@FreeBSD.ORG Sun Aug 29 08:06:13 2010 Return-Path: Delivered-To: svn-src-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E71A10656A5; Sun, 29 Aug 2010 08:06:13 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (brucec-2-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:679::2]) by mx1.freebsd.org (Postfix) with ESMTP id 14ACA8FC0C; Sun, 29 Aug 2010 08:06:13 +0000 (UTC) Received: from unknown (client-82-31-24-1.midd.adsl.virginmedia.com [82.31.24.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 74A6E5F15; Sun, 29 Aug 2010 08:06:06 +0000 (UTC) Date: Sun, 29 Aug 2010 09:06:07 +0100 From: Bruce Cran To: Bruce Evans Message-ID: <20100829090607.00007cef@unknown> In-Reply-To: <20100829115717.G26978@delplex.bde.org> References: <201008281632.o7SGW18U036444@svn.freebsd.org> <20100829115717.G26978@delplex.bde.org> X-Mailer: Claws Mail 3.7.4cvs1 (GTK+ 2.16.0; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org, Bruce Cran Subject: Re: svn commit: r211936 - in head: bin/test lib/libc/net lib/libc/stdio lib/libc/stdlib lib/libc/sys lib/libipx libexec/ypxfr sbin/ipfw secure/lib/libcrypto/man share/man/man4 share/man/man9 usr.sbin/I... X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Aug 2010 08:06:13 -0000 On Sun, 29 Aug 2010 12:12:46 +1000 (EST) Bruce Evans wrote: > On Sat, 28 Aug 2010, Bruce Cran wrote: > > > Log: > > Fix incorrect usage of 'assure' and 'insure'. > > I think some of the `assure's are more correct than their replacement > of `ensure'. The difference is subtle -- my small 1960's English > dictionary starts by saying that both mean "make safe"; it gives > the meaning "make certain to happen" only for `ensure', and this is > usually the meaning that we want, but I read `assure' as saying a > little more -- that we have done the ensuring and that clients cant > trust us to have done it. > > At least in old drafts, both POSIX and C99 use both `assure' and > `ensure', but never `insure'. C99 only has 3 `assure's so it is > easier to analyze. I think 1 or 2 of them would be better as > `ensure'. But C99 also uses `assuredly'. It would be strange if an > assurance or satisfaction of an `assuredly' could not be done by > `assure'ing it. After talking with other people I can see that quite a few probably were correct - for example "assure a degree of consistency". Should all the assure -> ensure changes be reverted? -- Bruce Cran