🚀 go-pugleaf

In <4kr7b2$kcb@solutions.solon.com> stanr@tiac.net (Stan Ryckman) writes:
>[replacement example changing alloca() to malloc() and inserting free()
>also snipped]
>Your example is too simple; that's an obvious conversion.
>Much more difficult is where alloca() has been used in a loop, to
>(for example) build a linked list (or worse) on the stack, and
>"return" has been used to free all the spaghetti.

Another place where I've found alloca() very useful is to allocate
memory in a recursive descent parser for a simple calculator.
Instead of cluttering the code with error checks at every step and
having to free memory and pass error values back up the calling
chain, I just longjmp'd back to the top level parse() function
whenever one of the low level routines found an error.

So, just how non-portable and horrible is this?


Michael Gordon
--
Politicians are like nappies, both should be changed regularly
and for the same reason - graffito on a wall in Yeovil.