On Sat, Feb 8, 2014 at 11:28 AM, Fidel N <fidelpe...@gmail.com> wrote:
>
> What if every definition were to be included as a new node, using @others
> for the code beneath.
>
This makes the fundamental problem worse.
The fundamental problem isn't that the imported data is wrong, it's that
important relationships get lost when data that belongs together gets split
into separate nodes.
My initial example was:
anIvar= False
def spam(self):
'''A method using anIvar.'''
foo = spam
It's bad style to split this into separate nodes, because then moving nodes
disrupts important adjacency relationships. Similarly, just putting base
classes into nodes that preceded subclasses creates a much-too-weak
precedence relationships between the classes. Such fine points don't
matter much for smallish scripts, but they matter a lot in million-line
code bases such as Leo's code.
Thus, it doesn't matter how we view an outline. What matters is that the
outline preserves essential relationships.
As Kent implies, less capable text editors don't need to worry about such
things because it's never possible to move code around by mistake. That
doesn't mean that the solution is to make it harder to move Leo nodes ;-)
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.
