From owner-freebsd-hackers Mon Feb 26 22:27:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from c62443-a.frmt1.sfba.home.com (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id B8E9E37B684 for ; Mon, 26 Feb 2001 22:27:52 -0800 (PST) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.9.3/8.9.3) id WAA17949; Mon, 26 Feb 2001 22:24:19 -0800 Date: Mon, 26 Feb 2001 22:24:19 -0800 From: Arun Sharma Message-Id: <200102270624.WAA17949@c62443-a.frmt1.sfba.home.com> To: dillon@earth.backplane.com Cc: hackers@freebsd.org Subject: Re: Setting memory allocators for library functions. In-Reply-To: <200102261755.f1QHtvr34064@earth.backplane.com> References: <200102260529.f1Q5T8413011@curve.dellroad.org> <200102261755.f1QHtvr34064@earth.backplane.com> Reply-To: adsharma@sharmas.dhs.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 26 Feb 2001 18:56:18 +0100, Matt Dillon wrote: > Ha. Right. Go through any piece of significant code and just see how > much goes flying out the window because the code wants to simply assume > things work. Then try coding conditionals all the way through to fix > it... and don't forget you need to propogate the error condition back > up the procedure chain too so the original caller knows why it failed. So, it all comes down to reimplementing the UNIX kernel in a language that supports exceptions, just like Linus suggested :) -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message