From: Ken A. <kan...@bb...> - 2002-04-23 17:13:32
|
Yes, some examples of what you find confusing would help. I do find that i get confused occasionally too. While we provide information about each stack frame things can get confusing if your deep in mapping functions or something, largely because closures print like: {jsint.Closure ??[1] (x)} Also, (let* ...) is turned into nested lambeda. I've started work on an unanalyzer which takes the compiled code and turns it back more toward the original scheme. Would that help? At 08:58 AM 4/23/2002, you wrote: >is there some way to make the JScheme error-backtrace a bit more explicit >about >exactly what's wrong? I generally don't get a message which I >understand...sometimes the messages are good, but sometimes the complaint >is so >vague as to be barely useful > >what would be better: well, something like the Allegro CL error output: >exactly >which fn-call had a problem, and maybe the argument that was bad or >something...I'd >have to gather examples to show exactly what I mean. > > -- clint |