Last night I realized the Python is, in some sense, the best language for @auto, because indentation matters in Python. This meshes perfectly with outline organization.
In contrast, languages such as C, javascript and html ignore indentation. @auto can still parse the sources into nodes, but @auto can't assume any default indentation scheme. Instead, to preserve the original indentation (or lack thereof), @auto will have to remember, for each node, the indentation that was removed to create that node. A uA is the obvious place for such data. In concept, his isn't a big deal, but in practice it will complicate the already way-too-complex code that checks the import to verify that rewriting the imported file will yield the same file. The comparison isn't necessarily strict. It depends on the language. I'll probably have to generalize the checking code, in an attempt to make it simpler. 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.
