TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Debugging Lisp Part 1: Recompilation

88 点作者 raphaelss将近 10 年前

2 条评论

pavelludiq将近 10 年前
On more than one occation when writing web code I found myself in the debugger in the middle of a request handler. The browser just sits there waiting for a response. I found the bug and restarted the handler before the browser time-outed. The browser recieved the response as if a bug never existed. Of course this only works if you can find and fix a bug in under 120 seconds :)
bainsfather将近 10 年前
As a non-lisp user, this {easy-debug -&gt; fix -&gt; resume program} appears to be extremely useful, and something that only lisp offers.<p>e.g. wading through clojure stack traces seems very primitive in comparison.<p>How important is it in practice? Can&#x2F;could other languages do this?<p>As an outsider looking at new (to me) languages, it&#x27;s hard to judge what the pros and cons of a language are - especially the cons - e.g. several years ago, when looking at clojure, it took a lot of searching before I concluded that clojure did <i>not</i> have this feature (maybe that has changed now?). Meanwhile the &#x27;learn language x&#x27; books always seem to focus only on syntax, rather than workflow.
评论 #9852340 未加载
评论 #9852546 未加载
评论 #9855086 未加载