back to the (ivory) tower

[der Mouse]

In article <500 at philmds.UUCP>, leo at 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 at mcgill-vision.uucp
			arpa: mouse at larry.mcrcim.mcgill.edu