Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-lcc!ames!ncar!oddjob!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.lang.c
Subject: alloca, longjmp
Keywords: alloca longjmp
Message-ID: <12915@mimsy.UUCP>
Date: 9 Aug 88 06:47:55 GMT
References: <895@vsi1.UUCP> <261@quintus.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 16

>In article <895@vsi1.UUCP> bitbug@vsi1 (James Buster) writes:
>>There is one reason to use alloca: longjmp.

In article <261@quintus.UUCP> ok@quintus.uucp (Richard A. O'Keefe) writes:
>There are a lot of other things one might want to clean up as well ....

>The answer is to put together something like Lisp's (unwind-protect ...),

The wheel turns (and on USENET, it has a short cycle :-) ).  I remember
proposing various mechanisms at least twice (once here or in unix-wizards,
once in comp.lang.c++).

An unwind-protect mechanism would indeed do the trick (and would allow
building higher level mechanisms, if desired).
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris