LIlispm·Mar 1, 2019
a more complex attempt at a Common Lisp in Prolog:
https://github.com/TeamSPoon/wam_common_lisp
In Interpreter for a simple Lisp, Written in Prologlogicmoo
wam_common_lisp
Common Lisp2017–2019
logicmoo / wam_common_lisp
wam_common_lisp
Allow Lisp programs to stop implementing an ad-hoc, informally-specified, bug-ridden, slow implementation of less than half of ISO-Prolog.
4Distinct people
6Mentions
0Explicit recommenders
104GitHub stars
What to know before exploring
What it is
Allow Lisp programs to stop implementing an ad-hoc, informally-specified, bug-ridden, slow implementation of less than half of ISO-Prolog.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month6 dated mentions
Observed mentions: 2017-11-12 19:50:06 UTC to 2019-03-01 12:29:13 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Nov 2017 | 2017-11-01 00:00:00 UTC | 2017-12-01 00:00:00 UTC | 2 | 0 | 2 |
| Dec 2017 | 2017-12-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2018 | 2018-01-01 00:00:00 UTC | 2018-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2018 | 2018-02-01 00:00:00 UTC | 2018-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2018 | 2018-03-01 00:00:00 UTC | 2018-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2018 | 2018-04-01 00:00:00 UTC | 2018-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2018 | 2018-05-01 00:00:00 UTC | 2018-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2018 | 2018-06-01 00:00:00 UTC | 2018-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2018 | 2018-07-01 00:00:00 UTC | 2018-08-01 00:00:00 UTC | 1 | 0 | 1 |
| Aug 2018 | 2018-08-01 00:00:00 UTC | 2018-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2018 | 2018-09-01 00:00:00 UTC | 2018-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2018 | 2018-10-01 00:00:00 UTC | 2018-11-01 00:00:00 UTC | 1 | 0 | 1 |
| Nov 2018 | 2018-11-01 00:00:00 UTC | 2018-12-01 00:00:00 UTC | 1 | 0 | 1 |
| Dec 2018 | 2018-12-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2019 | 2019-01-01 00:00:00 UTC | 2019-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2019 | 2019-02-01 00:00:00 UTC | 2019-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2019 | 2019-03-01 00:00:00 UTC | 2019-04-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
6 sourcesAnd you can run Common Lisp inside prolog: https://github.com/TeamSPoon/wam_common_lisp
In Who Killed Prolog? (2010)There's also this: https://github.com/TeamSPoon/wam_common_lisp/tree/master/pro...
A (fairly complete) implementation of Common Lisp in Prolog
In Lisprolog – Interpreter for a Simple Lisp, Written in PrologCommon Lisp compiles to much more than just 'native'. Like C, LLVM, DLLs, ... and a has a bunch of exotic stuff like whole-program-to-C compilers, Common Lisp on the metal or Common Lisp on top of Prolog https://github.com/TeamSPoon/wam_common_lisp .
Common Lisp also has full language interpreters: these are implementations of Common Lisp which interpret s-expression level code - not byte code.
Common Lisp can easily dump images and make them executable. Saving and starting them is quick.
Common Lisp has implementations mostly written in Common Lisp - including the compiler and large parts of the runtime.
In Practical Common Lisp (2009)OK, so now we are ready to answer the great-great-grandparent's question:
> Is SWI-Prolog really faster than CLisp?
No. At least not on naive Fibonacci.
[1]> (defun fib (n) (if (<= n 1) 1 (+ (fib (- n 1)) (fib (- n 2)))))
FIB
[2]> (compile 'fib)
FIB ;
NIL ;
NIL
[3]> (time (fib 38))
Real time: 6.730412 sec.
Run time: 6.732 sec.
Space: 0 Bytes
63245986
The project's GitHub page makes pretty much all the mistakes you can make when benchmarking: Comparing programs that are not equivalent and with wildly uncomparable optimization settings.
There is an almost incomprehensible blurb at the end of https://github.com/TeamSPoon/wam_common_lisp that (I think) tries to argue that you should not turn on optimization in Lisp because it costs more than you gain. I disagree.
In WAM-CL: Common Lisp in PrologThe link to the main github page, for the curious: https://github.com/TeamSPoon/wam_common_lisp
Is SWI-Prolog really faster than CLisp? I had no idea. Prolog seems like a language that would be pretty slow by default, but maybe you can do some pretty novel optimizations
In WAM-CL: Common Lisp in Prolog