Re: Slow clsql compilation
Nikodemus Siivola <[email protected]> Tue, 22 Aug 2006 17:44:18 +0300
| Newsgroups | gmane.lisp.steel-bank.devel,gmane.lisp.clsql.devel |
|---|---|
| Message-ID | <[email protected]> |
Sidney Markowitz <[email protected]> writes: > Nikodemus Siivola wrote, On 23/8/06 2:12 AM: >> There are some things that we could still do: for example making >> (> debug speed) inhibit inline-expansion might help with this. > > Wouldn't you want that anyway with high debug levels to allow tracing, > stepping, and backtraces to be more useful during debugging? Probably. For stepping it depend on the policy the original function was compiled with -- if it had a low debug policy, then inlining it would actually improve the STEP-experience. ...but for backtraces and tracing, definitely. Cheers, -- Nikodemus Schemer: "Buddha is small, clean, and serious." Lispnik: "Buddha is big, has hairy armpits, and laughs." ------------------------------------------------------------------------- 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