🚀 go-pugleaf

In article <4kr7b2$kcb@solutions.solon.com>, stanr@tiac.net (Stan Ryckman) writes:

|> alloca() is also similarly situated.  In "simple" cases, you
|> can use it and it seems like a function, but you can't do
|> everything with it that you can do with other functions; it's not
|> a full-fledged function.  I forget what breaks it exactly, but passing
|> a pointer to it certainly makes implementation a mess for some
|> architectures.

It's unwise to call alloca when evaluating actual arguments of a function call,
since this will put the buffer smack in the middle of the argument passing
area on the stack.   (If you're sure that your target compilers don't
pass arguments in registers (very rare), you might be able to use this to pass a
run-time variable number of arguments.)

Konrad Schwarz