On 27-Dec-05, at 6:31 PM, Christian wrote:
I'm thinking about writing a 'lowlevel' macro-expansion system which tracks source location (as I've mentioned in a mail a few weeks ago). That would help with problem 1 (it would directly show the relevant line).
My other suggestions would be: - (2) show the invalid macro-expanded code in the error message - (3) would it be feasible to compile the gambit core with `debug ? - (5) are there hooks into the builtin macro-expander? (to be able to grab the partially macro-expanded code oneself)
What Gambit really needs is an implementation of syntax-case that tracks source location information. It has been on my TODO list for a while, and I have a few bits and pieces working, but still far from a complete implementation. Marc