jsmacro 0.2 was a full rewrite (because version 0.2′s are always a full rewrite.) It’s now a little closer to what I was originally thinking. Instead of a line-by-line state machine, the parser now uses regex, and dynamically calls macro-handling methods based on the name of the macro. That’s a little vague, but in practice it means that extending the macro language is easier, and it may be possible to do it on-the-fly (as in, writing new macro implementations within the JavaScript source file that’s being parsed — which is a geeky goal I’m going for.)
Other new additions:
- Test files are now picked-up automatically when named correctly. This makes it painless to add more tests.
- Added support for setting DEFINE flags from the command-line. Handy if you automate builds for different environments (like IE6 vs. the rest of the world.)
- Added support for #ifdef and #ifndef
The next big hurdles will be how to handle else statements, and coming up with a reason to implement some type of #inline capability.