On Wed, 2 Jun 2010 05:01:24 -0700 (PDT)
zpcspm <[email protected]> wrote:
> As you can see, the line "m1 = method1()" landed into the second
> child.
I think that leo really only sees the def and class blocks, and just punts on
where to put the stuff that comes between them. A @decorator should obviously
go with the thing that follows it. But for comments and statements there's no
way for leo to know what makes sense.
class t(object):
def m1(self):
pass
m = m1
def m2(self, func=m):
print func
I know that's a weird piece of code, but I think you could argue the m = m1
belongs with the m2 definition in that case.
Cheers -Terry
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
