From owner-freebsd-current Tue Dec 9 09:21:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA17108 for current-outgoing; Tue, 9 Dec 1997 09:21:19 -0800 (PST) (envelope-from owner-freebsd-current) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA17100 for ; Tue, 9 Dec 1997 09:21:05 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id SAA00774; Tue, 9 Dec 1997 18:18:45 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Charles Henrich cc: perhaps@yes.no, freebsd-current@FreeBSD.ORG Subject: Re: VM system info In-reply-to: Your message of "Tue, 09 Dec 1997 11:43:31 EST." <199712091643.LAA04851@crh.cl.msu.edu> Date: Tue, 09 Dec 1997 18:18:45 +0100 Message-ID: <772.881687925@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>(5) Code prerequisites is documented through assert() or similar >> functionality. > >Egads! I wish assert() was thrown down to the pits of hell. Its a >programmers cop out. In almost no circumstance does one ever need to assert >. >If you find an error condition, COPE as best you can! Especially in the >kernel. Well, suffice to say that I disagree more than words can express. In particular in a kernel should assert be used to guard against "bad news", but lets just remember that an assert can be as stealthy as a syslog entry or as intrusive as a panic. It all depends exactly how bad. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop."