[Matthias Radestock <matthias@xxxxxxxxxx>]
>
> None of the above is checked in yet, and I doubt it will make it into
> the upcoming stable release. I would like to hear what people think of
> this stack tracer though. Would you find it useful? Have I missed any
> important feature? I am also interested in code examples that produce
> less-than-helpful error traces in previous/current SISC releases, so I
> can try the new stack tracer on these examples.
>
I would find this extremely useful. Relatively weak error messages are
one of the only problems I have with SISC. I don't have any specific
examples, although I noticed a bug opened recently that captures a few
of the common cases (where call info seems to be lost inside of "let"
and perhaps other forms). Anyway, yes I'd love to see traces like
these.
Thanks...
Matt
--
Matt Hellige matt@xxxxxxxxxx
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
|
