On Sep 2, 9:17 pm, Abdulaziz Ghuloum <[email protected]> wrote: <snip> > So, here you have (xform myform 'nonkeyword) expanding to > (xform (myform) 'nonkeyword) which does not match either > rule and causes a syntax violation. The step in the middle > does not have source information since it was constructed > by the xform macro, so, you can't get exact source position > for it. All Ikarus gives is the expansion steps (starting > from the first one which hopefully does have syntax info) > as you can see (reading the trace backwards): > > Unhandled exception > Condition components: > 1. &message: "invalid syntax" > 2. &syntax: > form: (xform (myform) 'non-keyword) > subform: #f > 3. &trace: #<syntax (xform (myform) 'non-keyword)> > 4. &trace: #<syntax (xform myform 'non-keyword) [char 270 of ./ > t.ss]> > > Makes sense? > > Aziz,,,
Yes and no. Unfortunately &trace is private and I cannot use it without parsing string representation of condition. Can &trace condition be made public ? Or you have reasons not to do it now ? BTW some time ago you sent utility to for using ikarus with vim. It looks like good use-case for making &trace public. -- Bogdan
