3 ms·
if you're having that much trouble debugging paren, put them all on their own lines and use indentation. then it'll be easy enough to fix.
by xlnt 19y ago
if you're having that much trouble debugging paren, put them all on their own lines and use indentation. then it'll be easy enough to fix.
- brlewis 19y agoIf he used an editor that auto-indented parens, he would probably be using an editor that had M-x forward-sexp and M-x backward-sexp too, so the debugging wouldn't be a problem. Still, 18-19 close parens sounds excessive. The source for ourdoings.com has 1 place with 9 close parens in a row, 4 places with 8, and 7 with 7. That's in 13KLOC.
- apgwoz 19y agoI looked and discovered you were using Jetty, does that mean you're using SISC or JScheme?
- brlewis 19y agohttp://brl.codesimply.net/ http://brl.codesimply.net/
- apgwoz 19y agoFunny, I didn't say Kawa because I've always assumed SISC was more popular... I didn't know about BRL though, thanks for the tip!
- brlewis 19y agoKawa can't capture continuations, so SISC definitely gets more attention. However, Kawa is way faster. If you read SISC's performance boasting you'll notice that it only compares itself to other Scheme interpreters on the JVM. Kawa is a compiler.