🚀 go-pugleaf

In article <1991Jan05.222639.6387@dirtydog.ima.isc.com> karl@ima.isc.com (Karl Heuer) writes:
>In article <1991Jan5.182428.615@mathrt0.math.chalmers.se> augustss@cs.chalmers.se (Lennart Augustsson) writes:
>>[In C extended with anonymous functions, we could write compose():]
>>	typedef int (*intintfun)(int);
>>	intintfun compose(intintfun f, intintfun g) {
>>	    return (int ANONYMOUS(int x) { return f(g(x))) };
>>	}
>>...the point is that you cannot add unnamed functions in a natural way
>>without getting the additional semantic power.
>
>I disagree.  Since the return value of the function references objects that go
>out of scope before the value would be used, I would expect this to analogous
>to   int *h(int i) { return &i; }   , which is undefined.
>
Do you think that 
	int f(int x, int y) { return x+y; }
is illegal just because the return statement contains variables that
goes out of scope when you return?
Returning an unnamed function is analogous (but I can imagine that an
implementer would like to make exactly your restriction since that would
make it much easier to implement).





	-- Lennart Augustsson
[This signature is intentionally left blank.]