From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 12 11:35:29 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 60A6C16A4DE for ; Wed, 12 Jul 2006 11:35:29 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from hydra.bec.de (www.ostsee-abc.de [62.206.222.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D539543D46 for ; Wed, 12 Jul 2006 11:35:28 +0000 (GMT) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (storm.stura.uni-rostock.de [139.30.252.72]) by hydra.bec.de (Postfix) with ESMTP id 9DE3F35707 for ; Wed, 12 Jul 2006 13:35:27 +0200 (CEST) Received: by britannica.bec.de (Postfix, from userid 1000) id 3D08D6D139; Wed, 12 Jul 2006 13:35:16 +0200 (CEST) Date: Wed, 12 Jul 2006 13:35:16 +0200 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org Message-ID: <20060712113516.GC2162@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org References: <44B2D2DF.2000401@sh.cvut.cz> <86sll8zl9x.fsf@xps.des.no> <86fyh8zgw8.fsf@xps.des.no> <868xn0z8w9.fsf@xps.des.no> <20060711152949.GB1463@merlin.emma.line.org> <1152642474.29859@origin.intron.ac> <3bbf2fe10607111437h6547432fn2887348708df29a4@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3bbf2fe10607111437h6547432fn2887348708df29a4@mail.gmail.com> User-Agent: Mutt/1.5.11 Subject: Re: kern/99979: Get Ready for Kernel Module in C++ X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2006 11:35:29 -0000 On Tue, Jul 11, 2006 at 11:37:52PM +0200, Attilio Rao wrote: > Even if I have no proof-of-concepts (so maybe somebody can show that > this is not fair), if we have setjmp/longjmp in the kernel we can have > a correct exception handling mechanism without not great problems. ROFL. Sorry, but using setjmp/longjmp is one of the worst possible implementation of exceptions since it is very expensive for the hot path, where you don't expect exceptions. They are called "exception" for a reason. Joerg