On Tue, 15 Jun 2010 11:09:22 -0500 "Edward K. Ream" <[email protected]> wrote:
> On Tue, Jun 15, 2010 at 9:56 AM, Terry Brown <[email protected]> wrote: > > >I think everything in its own node and if people don't like it they can use > >@shadow or @thin (unless @thin is @file now, in which case @file :-) > > No. Too many nodes would be the worst possible "solution". @shadow or > @thin are irrelevant to this discussion. We can not remedy defects in > @auto by resorting to @thin! True, but I don't think there's any way @auto can know which def node a declaration belongs to, and I really don't think it should guess and potentially hide critical information. Like this: def doSomething(self): ... def doSomethingCachedVersion(self): ... doSomething = doSomethingCachedVersion Ok, not great code, but you see this kind of thing often enough. If the declaration is hidden in the def doSomethingCachedVersion node, you could spend years, perhaps decades :-), trying to debug the first definition of doSomething, seeing that would seem to be the active code (assuming calls to self.doSomething elsewhere). I don't think auto can put declarations in def nodes without risking concealment of critical info. 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.
