Talk:First class environments: Difference between revisions
Content added Content deleted
(Not a closure) |
(Pointers vs. values) |
||
Line 1: | Line 1: | ||
So it's what, the thing we normally call "closure"? --[[User:Ledrug|Ledrug]] 09:14, 30 June 2011 (UTC) |
So it's what, the thing we normally call "closure"? --[[User:Ledrug|Ledrug]] 09:14, 30 June 2011 (UTC) |
||
:No, because a closure cannot be handled independently from the code, e.g. stored in a variable and activated at some other time with a piece of code.--[[User:Abu|Abu]] 09:19, 30 June 2011 (UTC) |
:No, because a closure cannot be handled independently from the code, e.g. stored in a variable and activated at some other time with a piece of code.--[[User:Abu|Abu]] 09:19, 30 June 2011 (UTC) |
||
Concerning the question whether the C solution "fits the spirit": I would say yes, though instead of switching the pointers to 'sec' and 'cnt' I would save and restore the actual values. This would better simulate the "binding" of the "environments".--[[User:Abu|Abu]] 15:17, 30 June 2011 (UTC) |
Revision as of 15:17, 30 June 2011
So it's what, the thing we normally call "closure"? --Ledrug 09:14, 30 June 2011 (UTC)
- No, because a closure cannot be handled independently from the code, e.g. stored in a variable and activated at some other time with a piece of code.--Abu 09:19, 30 June 2011 (UTC)
Concerning the question whether the C solution "fits the spirit": I would say yes, though instead of switching the pointers to 'sec' and 'cnt' I would save and restore the actual values. This would better simulate the "binding" of the "environments".--Abu 15:17, 30 June 2011 (UTC)