On Tue, Feb 18, 2014 at 6:13 AM, Reinhard Engel < [email protected]> wrote:
> >> ===== Handling leading whitespace >> ... >> > Handling leading indentation correctly leads to unavoidable >> complications. These won't go away in the new code, but perhaps they will >> be handled more cleanly. >> >> 1. Intermixed leading spaces and tabs are always going to cause problems >> of one kind or another. The code took one of various policies, including >> at least the following: >> >> - Automatically regularize leading whitespace, with or without a warning. >> - Refusing to remove leading indentation containing intermixed leading >> whitespace, with or without generating an @ignore directive. >> >> At present, both the code generators and the perfect import code choose >> different policies depending on the language in effect. The "strict" ivar >> determines whether leading whitespace is significant. However, leading >> whitespace can be significant in strings even in non-strict languages, a >> fact that I'm not sure the present code handles properly. >> ... >> > ==== >> > > Maybe you take another look at the »expandtabs« Python function (see > https://groups.google.com/forum/#!topic/leo-editor/pnblo1ap9c4) > The problems are policy problems, not coding problems. EKR -- 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.
