I think another important thing to consider about the emulator other then the lexing and parsing and stuff it extensibility. I am actually writing compiler for a new language to the DCPU and really there is almost no point in having to write another emulator IDE sort of thing for it. That essentially would be trying to rewrite what you are doing right now and is a waste of time. Since Herobrine, you are just writing it using Eclipse, I'm sure you could have some sort of plugin API system or something. The only thing that it would really need to have a source to assembly mapping for debugging, fancy syntax highlighting, and the actual compiler to integrate with it. Of course, my compiler itself is in the very early stages, but I think some other people would also like it to be extensible to allow other things to be added onto it versus have to rewrite the whole thing again. Probably something to consider later on, but I find it better to write a plugin for an emulator IDE system then to rewrite the entire thing all over again.
- RCP application
- Eclipse plugin
It might be a little more difficult to integrate your plugin with the application version, but the plan has always been to work toward increasing extensibility, so that will get easier over time, after I've added extension points specifically for facilitating that kind of extensibility.