@@ -221,16 +221,12 @@ are unusual for lexically scoped languages; there is typically a
221221mechanism to create name bindings (e.g. lambda and let in Scheme)
222222and a mechanism to change the bindings (set! in Scheme).
223223
224- XXX Alex Martelli suggests comparison with Java, which does not
225- allow name bindings to hide earlier bindings.
226224
227225Examples
228226========
229227
230228A few examples are included to illustrate the way the rules work.
231229
232- XXX Explain the examples
233-
234230::
235231
236232 >>> def make_adder(base):
@@ -289,8 +285,6 @@ The call to ``g()`` will refer to the variable i bound in ``f()`` by the for
289285loop. If ``g()`` is called before the loop is executed, a NameError will
290286be raised.
291287
292- XXX need some counterexamples
293-
294288Backwards compatibility
295289=======================
296290
@@ -479,8 +473,6 @@ straightforward manner, they are preferred.
479473Implementation
480474==============
481475
482- XXX Jeremy, is this still the case?
483-
484476The implementation for C Python uses flat closures [1]_. Each def
485477or lambda expression that is executed will create a closure if the
486478body of the function or any contained function has free
@@ -504,8 +496,6 @@ that access an enclosing scope is returned, should not prevent
504496unreferenced objects from being reclaimed by the garbage
505497collector.
506498
507- XXX Much more to say here
508-
509499References
510500==========
511501
@@ -517,7 +507,6 @@ References
517507Copyright
518508=========
519509
520- XXX
521510
522511..
523512 Local Variables:
0 commit comments