skip at pobox.com wrote: > By naming the function in which the binding is to occur you avoid problems > of someone coming along and adding or deleting functions between the > assignment (in baz) and the target of the assignment (x in foo) but then > forgetting to increment or decrement the counters that refer to a fixed > number of levels above the current function. But it doesn't do anything for the (I expect much more common) case of factoring out something in a function body and making it a nested function -- you'd still have to change the form of all the references to the name in that case. Better not to have a scheme that uses counters or scope names at all, I think. -- Greg
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4