From 16af557ae9c660cbd728546dcb28ec95b0030991 Mon Sep 17 00:00:00 2001 From: Jeremy Hylton Date: Thu, 18 Apr 2002 16:26:40 +0000 Subject: Remove more out-of-date comments and clarify explanation of visit(). --- Lib/compiler/visitor.py | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/Lib/compiler/visitor.py b/Lib/compiler/visitor.py index 934159b..52ea90d 100644 --- a/Lib/compiler/visitor.py +++ b/Lib/compiler/visitor.py @@ -26,13 +26,7 @@ class ASTVisitor: the order during a postorder walk, because it is called _after_ the walk has occurred.) The ASTVisitor modifies the visitor argument by adding a visit method to the visitor; this method can - be used to visit a particular child node. - - XXX The interface for controlling the preorder walk needs to be - re-considered. The current interface is convenient for visitors - that mostly let the ASTVisitor do everything. For something like - a code generator, where you want to walk to occur in a specific - order, it's a pain to add "return 1" to the end of each method. + be used to visit a child node of arbitrary type. """ VERBOSE = 0 -- cgit v0.12