Having that series of operations produce something useful is unexpected, to say the least.
It's nothing I'd want to see in code that I maintain, but I think you have to give it a bit more credit. Besides that, it's cute :)
Ian Lance Taylor replied that the behavior is
undefined, but so far stable. His suggestion was
to open a bug and request that this desirable (!!!)
behavior be explicitly permitted.If you call a nested function it has to know the frame address of the containing function in order to refer to its local variables. So if you take the address of such a function the program actually receives the address of a "trampoline": a small sequence of instructions which first loads the frame address and then calls the real function.
The trampoline itself is generated dynamically and putting it on the stack turns out to be cheaper than heap allocating it.
Well, more so that C has no concept of the heap. That's entirely contained within the C libraries. So, the language implementation itself can't do heap allocations (at least, not without sacrificing any chance of using it in embedded or kernel dev situations where you don't have heap allocation, or where you need to use custom allocators)
> Thus, if you access the enclosing environment, you
> must ensure that the lifetime of this lambda is bound by the
> lifetime of the enclosing environment (i.e., until the enclosing
> function returns). This means that if you access local
> variables, bad things will happen. If you don't access local
> variables, you're fine.
Might as well avoid the complications, hoist the function and pass a function pointer with some context (assuming it's needed).I do not find it obvious from that documentation that you can pass a compound statement expression as a function pointer.
And touche', I just glanced at the contents of the macro before replying.
http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_4.html#SEC62