Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mcgill-vision!mouse
From: mouse@mcgill-vision.UUCP (der Mouse)
Newsgroups: comp.unix.wizards
Subject: Re: back to the (ivory) tower
Message-ID: <1176@mcgill-vision.UUCP>
Date: 22 Jun 88 14:09:31 GMT
References: <16018@brl-adm.ARPA> <500@philmds.UUCP>
Organization: McGill University, Montreal
Lines: 20

In article <500@philmds.UUCP>, leo@philmds.UUCP (Leo de Wit) writes:
> But I have a nice alternative: lets always use alloca() and a new
> function, call it freea(), in pairs.
>     For [compilers] that don't [support alloca]:
> #define alloca malloc    /* the oldies */
> #define freea  free

Then why bother with alloca, if the semantics are such that malloc can
be used instead?

> Everybody happy?

No.  The people who use alloca to get automatic freeing on a longjmp
(or other stack unwind) won't be able to tolerate the malloc
replacement.

					der Mouse

			uucp: mouse@mcgill-vision.uucp
			arpa: mouse@larry.mcrcim.mcgill.edu