From: bert hubert <ahu@ds9a.nl>
To: Dan Aloni <da-x@gmx.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] [PATCH] C exceptions in kernel
Date: Sat, 23 Feb 2002 16:21:00 +0100 [thread overview]
Message-ID: <20020223162100.A1952@outpost.ds9a.nl> (raw)
In-Reply-To: <1014412325.1074.36.camel@callisto.yi.org>
In-Reply-To: <1014412325.1074.36.camel@callisto.yi.org>; from da-x@gmx.net on Fri, Feb 22, 2002 at 09:18:29PM +0000
On Fri, Feb 22, 2002 at 09:18:29PM +0000, Dan Aloni wrote:
> The attached patch implements C exceptions in the kernel, which *don't*
> depend on special support from the compiler. This is a 'request for
> comments'. The patch is very initial, should not be applied.
>
> I actually got this code to work in the kernel:
>
> try {
> printk("TEST: before throwing \n");
> throw(1000);
> printk("TEST: won't run\n");
> }
> catch(unsigned long, value) {
> printk("TEST: caught: %ld\n", value);
> } yrt;
Can they fall through multiple function calls? How do they jive with
preemtive scheduling? How much is the stack unwinding overhead?
Potentially this is very cool but I'm again appalled at the INSTANT
rejection seen here by kernel hackers, minor and major. Do NOT reject an
idea before you've thought it through. Do NOT reject an idea simply because
it is new.
Also, do not jump on the bandwagon BECAUSE it is new. But still - people
here should get a life if they get off on rejecting new stuff because it is
new.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
Linux Advanced Routing & Traffic Control: http://ds9a.nl/lartc
next prev parent reply other threads:[~2002-02-23 15:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1014437101.26721.linux-kernel2news@redhat.com>
2002-02-22 21:12 ` Dan Aloni
2002-02-22 21:28 ` Davide Libenzi
2002-02-22 22:10 ` Richard B. Johnson
2002-02-22 22:34 ` David B. Stevens
2002-02-22 22:48 ` Davide Libenzi
2002-02-23 3:37 ` Edgar Toernig
2002-02-23 10:11 ` Pete Zaitcev
2002-02-23 12:26 ` Keith Owens
2002-02-23 12:50 ` Pete Zaitcev
2002-02-23 23:07 ` Jes Sorensen
2002-02-23 23:40 ` Keith Owens
2002-02-24 1:02 ` Jes Sorensen
2002-02-24 23:45 ` Richard Gooch
2002-02-23 23:50 ` Bill Huey
2002-02-24 1:31 ` Davide Libenzi
2002-02-24 2:55 ` Bill Huey
2002-02-23 15:13 ` Felix von Leitner
2002-02-23 15:21 ` bert hubert [this message]
2002-02-23 17:47 ` Alexander Viro
2002-02-23 18:21 ` bert hubert
2002-02-23 18:31 ` Larry McVoy
2002-02-23 18:38 ` bert hubert
2002-02-23 19:12 ` Kurt Ferreira
2002-02-23 23:05 ` Jes Sorensen
2002-02-23 16:05 ` Dan Aloni
2002-02-23 16:22 ` Larry McVoy
2002-02-23 17:07 ` bert hubert
2002-02-23 17:00 ` Dan Aloni
2002-02-23 17:52 ` Francois Romieu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020223162100.A1952@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=da-x@gmx.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®