On Fri, Feb 26, 2010 at 8:08 PM, Edward K. Ream <[email protected]> wrote:
> In short, it should be possible to demonstrate a prototype (with unit > tests) in just a few hours. Done in the new-pylint branch at rev 16. Total programming time, about 4 hours. A lot of work remains, both substantive and packaging, but it is now clear that scanning is, by far, the simplest and most flexible way to munge code. Edward P.S. The PythonScanner class does both scanning and "semantic" processing. As of rev 16, I only use a single class. Previously, I used two subclasses, one for pass 1, and one for pass 2, but this was overkill. Now, a pass_n switch indicates the pass, and the various semantic methods do different things depending on this switch. This is considerably simpler and actually clearer than the subclass way. 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.
