On Aug 18, 10:54 pm, Paul McGuire <pt...@austin.rr.com> wrote: > Please post a link to the pyparsing wiki, I would be interested in seeing if > there are some pyparsing optimizations that might help. (I downloaded the > project source, but did not find any pyparsing code in it.)
I'm guessing this is in response to my email about doxylink? If so then you're correct that there's no pyparsing in version 0.4 but there will be in the next version which can be viewed at bitbucket. The file in question is http://bitbucket.org/birkenfeld/sphinx-contrib/src/tip/doxylink/sphinxcontrib/doxylink/parsing.py. I'm sure there are plenty of things I am doing wrong so I'll make a post at your wiki. Either way, there's a problem that for a large file (like from OGRE3D) there's about 16,000 calls to parseString() that needs to be made. Anyway, I'll take this away from the Sphinx list now and on to pyparsing. Matt -- You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to sphinx-...@googlegroups.com. To unsubscribe from this group, send email to sphinx-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en.
