On Tue, Jul 8, 2008 at 9:20 AM, Edward K. Ream <[EMAIL PROTECTED]> wrote:
> I consider @auto to be a most happy development. In particular, @auto > provides an excellent *starting* point for @shadow. > @auto does one (important!) thing more: it guarantees that the result of writing an @auto file will be identical (up to some specified 'strictness' level) to the original files. For 'strict' languages such as python, the comparison requires substantially identical leading whitespace. In other words, @auto isn't a lax import: when it succeeds it guarantees that we won't be changing the original (public) files. When it fails, it tells us why it failed so we could, for example, request that pypy clean up the offending files. I think this is *exactly* the right balance to have when dealing with external projects, especially Python projects. EKR --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
