26 Nov
2008
26 Nov
'08
18:55
Hi all! Is there a way to debug a macro expansion? More precisely, I'd like to be able to have access to the full debugger when my macro expansion fails such that I could trace what's wrong of the code producing the expansion... At the moment I get something like:
(pp (lambda () (define-class tata (toto) (slot: a)))) *** ERROR -- Unbound table key (table-ref '#<table #2> 'tata)
with no possibility to debug and see whats wrong. I guess that the environment is available at the expansion time so I don't see why I couldn't debug it like normal gambit code. Many thanks in advance ^_^Y David