From owner-svn-src-all@FreeBSD.ORG Sun Aug 29 02:12:50 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 5A7D710656A8; Sun, 29 Aug 2010 02:12:50 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail03.syd.optusnet.com.au (mail03.syd.optusnet.com.au [211.29.132.184]) by mx1.freebsd.org (Postfix) with ESMTP id CFC0C8FC19; Sun, 29 Aug 2010 02:12:49 +0000 (UTC) Received: from c122-107-127-123.carlnfd1.nsw.optusnet.com.au (c122-107-127-123.carlnfd1.nsw.optusnet.com.au [122.107.127.123]) by mail03.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id o7T2Ckxh010528 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 29 Aug 2010 12:12:47 +1000 Date: Sun, 29 Aug 2010 12:12:46 +1000 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Bruce Cran In-Reply-To: <201008281632.o7SGW18U036444@svn.freebsd.org> Message-ID: <20100829115717.G26978@delplex.bde.org> References: <201008281632.o7SGW18U036444@svn.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org 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 02:12:50 -0000 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. Bruce