Path: news.cs.au.dk!not-for-mail From: nospam2159@cs.au.dk (Peter von der =?iso-8859-1?q?Ah=E9?=) Newsgroups: comp.lang.beta Subject: Re: Static vs. dynamic exceptions Date: 20 Jun 2000 17:35:28 +0200 Organization: Computer Science Department of the University of Aarhus Lines: 26 Message-ID: References: <20000619173848.8485.qmail@noatun.mjolner.dk> <8im02p$8s5j$1@xinwen.cs.au.dk> <8infta$9jn7$1@xinwen.cs.au.dk> <394F9765.21D28D31@skynet.be> <394FB1CE.F9E6A96D@skynet.be> NNTP-Posting-Host: ufleku.cs.au.dk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: xinwen.cs.au.dk 961515328 284940 255.255.255.255 (20 Jun 2000 15:35:28 GMT) X-Complaints-To: news@cs.au.dk NNTP-Posting-Date: 20 Jun 2000 15:35:28 GMT X-Attribution: Ahe User-Agent: Gnus/5.0806 (Gnus v5.8.6) Emacs/20.6 Xref: news.cs.au.dk comp.lang.beta:12464 >>>>> "A" == Atle writes: A> Managing control flow - setting up interrupt (exception handlers), A> implemented somewhat like interrupt time/task time processes in a A> device driver .... I think you confuse dynamic exceptions with processor interrupts or traps. The latter is more like signals. Dynamic exceptions are similar to setjmp/longjmp in C, but more safe, as interleaving is disallowed and resources are freed automatically. By interleaving I mean a program trace like: setjmp(A) .... setjmp(B) .... longjmp(A) .... longjmp(B) I do not know if this is legal in C, but you can write code that will try to do so. -- YMMV