Work is going extremely well. I expect to complete the conversion of the Python importer in a day or so.
I have put a huge amount of work into the infrastructure of the code. The new code is much simpler than the old, and more flexible. As mentioned elsewhere, code generation now happens in three explicit pipeline stages. A few unit tests fail with the V2 switch on in python.py. They should be relatively easy to fix. The new infrastructure (API for setting body text) should easily some remaining special cases: - python decorators - C functions whose signatures extend for several lines *before* the curly brackets that start their body. These involve scanning backward by whole lines. The old code scanned by characters, which amounts to fully parsing the languages for which such things mattered. When all tests pass with the new Python importer, the only remaining task will be to convert 14 or so other scanners. The present infrastructure should make this straightforward. Maybe an hour per language. 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
