**Warning**: Please skip this post if you don't like developer discussions.
On Apr 6, 1:32 pm, "Ville M. Vainio" <[email protected]> wrote: > On Wed, Apr 6, 2011 at 6:58 PM, Edward K. Ream <[email protected]> wrote: > > > 2. Super lintoffers the possibility of speeding up important parts of > > Leo by converting them to [Cython] automatically. > > I'm 95% sure this is not going to help. > > The parts that would most benefit from optimization (node iteration, > @file parsing) are much easier to hand-optimize (with cython/c/c++) > than by trying to create some automatic scheme. Any automatic scheme > would just point out the things that are trivial anyway (e.g. "this is > an int"). This continues to be an "inspiring" comment, though I don't (yet :-) agree with all parts of it. I have just posted a lengthy set of musings about this in the "Leo and Pylint" group: http://groups.google.com/group/leo-and-pylint/browse_thread/thread/c71ab567d6eb82e7/6bf761754957037b#6bf761754957037b A short summary: A. I agree that automatic conversion of Python to Cython will not be easy. I have not given up, but significant invention is required. B. I continue to assert that type checking is possible and useful. C. I have *zero* interest in hand-written C code, even if disguised as Cython code. C requires heroic unit testing to be safe. However, it may be possible, with appropriate helper programs and Cython settings, to guarantee Python-like safety in *some* kinds of Cython files. D. I have *zero* interest in maintaining two code bases for any part of Leo. In short, the way forward is murky, but fascinating. Some obvious first steps: - Explore what kinds of safety-checks can be built into Cython code. - Explore thought experiments re generating Cython code from Leo's sources, possibly containing hints or other "cheats". Edward -- 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.
