Hi Christian. You're right, comments are what I'm looking for. I just want to add to what you said, that the scanner is 100% ANSI C (look at abcpscan.re not at abcpscan.c!).
The next big decision to take is if the whole parser should be in C or if I should start using Lua right now. Consider the discussions on the list about T: and K:. If the parser was in C, we had to recompile it to make it accept one (or all) of the proposed semantic, would it be in Lua, one could simply change the script and run the parser again. On the other hand a parser in C would be easier to embed. But we could keep something in Lua and then rewrite in C when everyone agrees on that particual piece of syntax. But if it was in Lua, one could provide a script to transform a file that use a no-longer supported syntax into a file that follows the standards. But should it be an external tool or should be left up to the user? But, .. but... but. There are countless scenarios to consider and evaluate!!! .RD. To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
