> On Wed, Dec 3, 2008 at 3:55 PM, Michal Kwiatkowski >> Below some more links that may be of interest: >> >> http://time-loop.tumblr.com/post/47664644/python-ast-preserving-whitespace-and-comments >> (the reason why I've chosen lib2to3) >> http://nedbatchelder.com/blog/200804/the_structure_of_pyc_files.html >> http://nedbatchelder.com/blog/200804/wicked_hack_python_bytecode_tracing.html >> http://thermalnoise.wordpress.com/2007/12/30/exploring-python-bytecode/
I am a hacker (in the old sense of bit-fiddler) at heart :-) As it happens, I am the one who suggested removing the old c_lineno opcode. I didn't know how it morphed into a line number table. Iirc, it was in comp.lang.python that I suggested a possible 5% speedup in Python by removing this opcode. I haven't been able to track down the thread. I would be grateful if somebody could find this: it's probably the reason I'm mentioned in the Python acknowledgments. BTW, the @shadow code is line-oriented because it uses line-oriented diffs. Thus, the whitespace issues had to be solved by brute force. Using the ast was not an option. 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 -~----------~----~----~----~------~----~------~--~---
