Re: changing the macro expander

> nice error reporting is in place - is a nightmare,

Speaking of nice error reporting, are there any
improvements on that front? Because, even as late as
1.16.5, I have not had any encounters with the SISC
error reporting mechanism that could be described as
"nice".

[ Granted, the other schemes I work with are no
better. ]

I don't have any output snippets handy, but to
summarize my (recent) traumas:

* without disabling the suppressed-source-kinds
filter, I get one stack frame (or even nothing)

* when I eliminate the suppression, I get lots of
?:?:? nonsense frames.

I might be overly simiplistic, but to me it's very
clear what frames should be printed:

* frames that correspond to Scheme code (not Java
c**p) should always be printed.

* if the frame refers to a named function/lambda, give
the name

* in all cases, print the source file, line and column
where the named/anonymous lambda is defined

A further suggestion: make the default printer for
procedures output something like

#<procedure proc (source-file.scm:23:12, 2 args)>

All the above would apply only to cases when debugging
is turned on. I realize that debug is disabled by
default for performance reasons.

-- Dan



 
____________________________________________________________________________________
Sponsored Link

$200,000 mortgage for $660/mo - 30/15 yr fixed, reduce debt, home equity - 
Click now for info http://yahoo.ratemarketplace.com

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642