From owner-freebsd-hackers Mon Jul 29 18:19:11 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA04660 for hackers-outgoing; Mon, 29 Jul 1996 18:19:11 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA04655 for ; Mon, 29 Jul 1996 18:19:09 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id BAA03141 for ; Tue, 30 Jul 1996 01:19:07 GMT Date: Tue, 30 Jul 1996 10:19:07 +0900 (JST) From: Michael Hancock To: FreeBSD hackers Subject: Re: kernel assertions In-Reply-To: <199607292004.WAA04122@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 29 Jul 1996, J Wunsch wrote: > As Michael Hancock wrote: > > > Assertions are the most under-rated software engineering tool I can think > > of. > > But also the IMHO most misnamed tool in the standard. It's (at least > for me as a non-native speaker) absolutely unobvious what happens for > which condition. I had a French professor who decided to call them, REQUIRE and ENSURE. [Function declaration] [REQUIRE: Don't give me bogus arguments or I'll stop] [REAL CODE] ... [ENSURE: I'll guarantee this or I'll stop] [End]