tag:blogger.com,1999:blog-18508356.post8646679290917812355..comments2026-02-13T11:24:21.556-05:00Rick Copelandhttp://www.blogger.com/profile/11612114223288841087noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-18508356.post-91886342413934059902009-05-03T11:20:00.000-04:002009-05-03T11:20:00.000-04:00@fivebells: Not yet -- any chance I could get you to write a feature request at http://code.google.com/p/metapython/issues/entry ?Rick Copelandhttps://www.blogger.com/profile/11612114223288841087noreply@blogger.comtag:blogger.com,1999:blog-18508356.post-4247835336842716332009-05-03T11:18:00.000-04:002009-05-03T11:18:00.000-04:00Thanks for the information, Rick. Does MetaPython have that dumping capability?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-18508356.post-65223867559980349682009-05-03T11:14:00.000-04:002009-05-03T11:14:00.000-04:00@fivebells: I haven't actually done a lot of experimentation with the debugger, so my guess is "not very well." Macro debugging is, in general, difficult since the code at runtime is not the same code you originally wrote. To aid in debugging somewhat, a MetaPython module has a special attribute __expanded__ that represents the Python code that all the macros in the source expand out to. <br /><br />One debugging trick that may be useful to add is the ability to dump out a standard .py file from a .mpy file and use that for debugging. Then at least you're dealing with "regular" Python instead of a weird exec'd string of Python code.Rick Copelandhttps://www.blogger.com/profile/11612114223288841087noreply@blogger.comtag:blogger.com,1999:blog-18508356.post-92107326488220150552009-05-02T22:54:00.000-04:002009-05-02T22:54:00.000-04:00This looks very interesting. How do the macros interact with the debugger?Anonymousnoreply@blogger.com