Right now I'm faced with the daunting task of writing a code analyzer that takes a DM file and processes it line-by-line to get a list of available objects, procs, and vars.

There's an option in dm.exe that allows you to print an object tree in XML format, but when dealing with large projects such as SS13 this is horribly slow.

I'm hoping to avoid having to write something myself, but instead use the compiler to process the project files instead, while maintaining a good speed even in large projects.

I don't know where the bottlenecks are that cause the compiler to be so slow when dealing with projects such as SS13. I know that I don't actually need the compiler to create a .dmb/.rsc file for me, all I'm interested in is any errors/warnings and the full object tree with all possible procs/vars for the project including built-in procs and vars.

If it's not feasible to make the tool any faster, would it be possible to allow for incremental compilation? How I think it would work is that the dm.exe tool would process everything at first the way it does now, but allow saving the results to a file. Later I could call the tool with the results file and a list of modified files, and it would only scan the modified files for changes and apply them to the existing resultset.

And if that's not feasible then I'd like it if (parts of) the Dream Maker source-code could be provided (at least for me if not open-source) so I can copy the parts that analyse code / generate the object tree from that.

Is any of this possible?