>the point of the analysis step is to generate a richer (more verbose) >set of information about the code, there is a lot of information you >would like to have when compiling (for example, for some platforms it >would be nice to know at the start of a function what locals exist in >the that function, or what locals it closes over)
Ah yes, that makes sense. Well that's going to be a good point to start I think. And it looks like I can just hack the compiler.clj to output json (or something close to that). From there I should be able to whip out at Python emitter in no time. Timothy -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
