On Tue, Dec 24, 2013 at 10:10 AM, Terry Brown <[email protected]>wrote:
>
So will @auto still have close to zero impact on collaborated files?
That's the intention.
However, your comment, and Matt's, makes me wonder whether I'm moving in
the right direction.
It's easy to get carried away with coding considerations and miss the big
picture.
Perhaps explicit section references just won't work, no matter how light
the markup. In that case, a rethink of the new Python importer would be in
order.
At present, the scheme separates code into separate nodes for each class or
def, but the side effect of that is that multiple section references or
@others might be generated for a single node. This won't work if there is
no way to represent section references.
The alternative would be to ensure that no node will ever contain more than
one @others directive. This can be done as follows:
1. Put all top-level code preceding the first class or def *at the top
level* into a "preamble" node. This would handle the case:
if 0:
def spam(): pass
2. Have each def include all nested classes & defs.
The combination of these two rules (perhaps recursively applied for
classes) should ensure that no node will contain more than one @others
directive.
I'll have to give this whole issue some more thought. Thanks for your
comments.
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.
