…debug your programs by logical reasoning. In fact, to a significant extent, you can even automate debugging due to these properties. Such techniques were pionereed by Ehud Shapiro in his 1982 PhD thesis, Algorithmic Program Debugging: http://cpsc.yale.edu/sites/default/files/files/tr237.pdf The thesis is an excellent read, and I highly recommend it! Specifically, quoting from page 155: “Although Lisp is considered a high level…
这确实是一种极其有趣的方法。它最初是由 Ehud Shapiro 在其 1982 年的博士论文《Algorithmic Program Debugging》中，结合逻辑编程和 Prolog 开创出来的。该论文被 MIT 出版社作为 ACM 杰出博士论文出版，可以在线获取：http://cpsc.yale.edu/sites/default/files/files/tr237.pdf 与 Leon Sterling 一起，Ehud……
This is indeed an extremely interesting approach. It was pioneered in the context of logic programming and Prolog by Ehud Shapiro in his 1982 PhD thesis "Algorithmic Program Debugging". The thesis was published as an ACM Distinguished Dissertation by MIT press and is available online from: http://cpsc.yale.edu/sites/default/files/files/tr237.pdf Together with Leon Sterling, Ehud…
The induction of logic programs in Prolog from examples was done by Ehud Shapiro's "Model Inference System" described in his PhD thesis, "Algorithmic Programming Debugging" (https://www.amazon.com/Algorithmic-Program-Debugging-Disting...), in 1982. This was one of the earliest inductive logic programming (https://en.wikipedia.org/wiki/Inductive_logic_programming) systems.
…debug both cases very systematically and even automatically, using built-in mechanisms of the language. Declarative debugging methods for Prolog were pioneered by Ehud Shapiro in his 1982 PhD thesis, Algorithmic Program Debugging: https://cpsc.yale.edu/sites/default/files/files/tr237.pdf I also highly recommend Ulrich Neumerkel's teleteaching environment GUPU for systematically finding mistakes in Prolog programs: https://www.complang.tuwien.ac.at/ulrich/gupu/
Possibly interesting trivium: automated debugging was first described in 1982, in Ehud Shapiro's PhD thesis titled "Algorithmic Program Debugging" (it's what it sounds like and it can also generate programs by "correcting" an empty program): https://en.wikipedia.org/wiki/Algorithmic_program_debugging Of course all this targeted only Prolog programs…
…unit tests, or] look over your code and understand and explain where you might have bugs. What you're describing (outside of the square braces) is algorithmic debugging: https://en.wikipedia.org/wiki/Algorithmic_program_debugging It was introduced in the PhD thesis of Ehud Shapiro. There's been a steady trickle of research work since then but it's never formed into a strong current, if I may. One reason for that is of course…
……通过逻辑推理来 debug 你的程序。事实上，由于这些特性，你甚至可以在很大程度上实现自动化调试。这类技术是由 Ehud Shapiro 在他 1982 年的博士论文《Algorithmic Program Debugging》中开创的：http://cpsc.yale.edu/sites/default/files/files/tr237.pdf 这篇论文非常值得一读，我强烈推荐！具体来说，引用第 155 页的内容：“尽管 Lisp 被认为是一种高级……
…debug your programs by logical reasoning. In fact, to a significant extent, you can even automate debugging due to these properties. Such techniques were pionereed by Ehud Shapiro in his 1982 PhD thesis, Algorithmic Program Debugging: http://cpsc.yale.edu/sites/default/files/files/tr237.pdf The thesis is an excellent read, and I highly recommend it! Specifically, quoting from page 155: “Although Lisp is considered a high level…
这确实是一种极其有趣的方法。它最初是由 Ehud Shapiro 在其 1982 年的博士论文《Algorithmic Program Debugging》中，结合逻辑编程和 Prolog 开创出来的。该论文被 MIT 出版社作为 ACM 杰出博士论文出版，可以在线获取：http://cpsc.yale.edu/sites/default/files/files/tr237.pdf 与 Leon Sterling 一起，Ehud……
This is indeed an extremely interesting approach. It was pioneered in the context of logic programming and Prolog by Ehud Shapiro in his 1982 PhD thesis "Algorithmic Program Debugging". The thesis was published as an ACM Distinguished Dissertation by MIT press and is available online from: http://cpsc.yale.edu/sites/default/files/files/tr237.pdf Together with Leon Sterling, Ehud…
在 Prolog 中通过示例归纳逻辑程序是由 Ehud Shapiro 在其 1982 年的博士论文《Algorithmic Programming Debugging》（https://www.amazon.com/Algorithmic-Program-Debugging-Disting...）中描述的“模型推断系统”（Model Inference System）实现的。这是最早的归纳逻辑编程（https://en.wikipedia.org/wiki/Inductive_logic_programming）系统之一。
The induction of logic programs in Prolog from examples was done by Ehud Shapiro's "Model Inference System" described in his PhD thesis, "Algorithmic Programming Debugging" (https://www.amazon.com/Algorithmic-Program-Debugging-Disting...), in 1982. This was one of the earliest inductive logic programming (https://en.wikipedia.org/wiki/Inductive_logic_programming) systems.
……利用语言的内置机制，非常系统化甚至是自动化地 debug 这两种情况。Prolog 的声明式调试方法是由 Ehud Shapiro 在其 1982 年的博士论文《Algorithmic Program Debugging》中开创的：https://cpsc.yale.edu/sites/default/files/files/tr237.pdf 我也非常推荐 Ulrich Neumerkel 的远程教学环境 GUPU，用于系统地排查 Prolog 程序中的错误：https://www.complang.tuwien.ac.at/ulrich/gupu/
…debug both cases very systematically and even automatically, using built-in mechanisms of the language. Declarative debugging methods for Prolog were pioneered by Ehud Shapiro in his 1982 PhD thesis, Algorithmic Program Debugging: https://cpsc.yale.edu/sites/default/files/files/tr237.pdf I also highly recommend Ulrich Neumerkel's teleteaching environment GUPU for systematically finding mistakes in Prolog programs: https://www.complang.tuwien.ac.at/ulrich/gupu/
可能挺有意思的冷知识：自动化调试最早是在 1982 年 Ehud Shapiro 题为《Algorithmic Program Debugging》的博士论文中提出的（顾名思义，它甚至可以通过“修正”一个空程序来生成程序）：https://en.wikipedia.org/wiki/Algorithmic_program_debugging 当然，这一切当时只针对 Prolog 程序……
Possibly interesting trivium: automated debugging was first described in 1982, in Ehud Shapiro's PhD thesis titled "Algorithmic Program Debugging" (it's what it sounds like and it can also generate programs by "correcting" an empty program): https://en.wikipedia.org/wiki/Algorithmic_program_debugging Of course all this targeted only Prolog programs…
……单元测试，或者] 查看你的代码，理解并解释你哪里可能会有 bug。你所描述的（方括号之外的内容）就是算法调试（algorithmic debugging）：https://en.wikipedia.org/wiki/Algorithmic_program_debugging 这是在 Ehud Shapiro 的博士论文中提出的。从那时起，这方面的研究工作一直细水长流，但恕我直言，它从未形成一股强劲的主流浪潮。其中的一个原因当然是……
…unit tests, or] look over your code and understand and explain where you might have bugs. What you're describing (outside of the square braces) is algorithmic debugging: https://en.wikipedia.org/wiki/Algorithmic_program_debugging It was introduced in the PhD thesis of Ehud Shapiro. There's been a steady trickle of research work since then but it's never formed into a strong current, if I may. One reason for that is of course…