I uncommented this line, and I tried with both these commands. Cython dummy.pyx Cython -v dummy.pyx and it did not generate any verbose output.The output was same as before, without uncommenting that line. Am i missing something ?
On Sat, Mar 14, 2009 at 6:52 AM, Robert Bradshaw < [email protected]> wrote: > On Mar 13, 2009, at 1:45 PM, Stefan Behnel wrote: > > > comer c wrote: > >> I was looking at the cython compiler code, after sometime i got > >> lost tracing > >> it. > > > > Yes, there is a lot of code, and it's not always trivial to trace > > into it. > > > > > >> What is the best way to trace/analyze the code?For example if i > >> want to see > >> the different phases of the compiler like the tokenizer,parser and > >> code > >> generator?Can you provide me the proper way to begin with code > >> analzing. > >> Much help appreciated in this regard. > > > > Have you looked into the compiler pipeline in Main.py? (~line 110). > > It runs > > after the parser, but the most interesting stuff happens there, > > actually. > > Just set a break point into a class that looks interesting and see > > what it > > does with the tree. To print the tree, call "node.dump()" at any > > time, or > > put a "PrintTree()" into the pipeline at any point. > > For the code generation phase, you can uncomment the lines > > # Uncomment this for debugging. > # __metaclass__ = VerboseCodeWriter > > In Node.py:119-120, which will very verbosely annotate the output > (though it hasn't been fully debugged--sometimes the resulting file > won't compile). > > - Robert > > _______________________________________________ > Cython-dev mailing list > [email protected] > http://codespeak.net/mailman/listinfo/cython-dev >
_______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
